Re: Re^3: Distinguishing a v-string from something else

Re: actually, they're UTF-8 encoded if they're above 255.

I just got around to verifying this. Actually, it does not work the same as chr, in that the v-string encoding faithfully follows the utf8 pragma, while chr decides for itself whether to return a byte or char oriented string regardless of the pragma setting.

I'm wondering, though, if a number without a v and only 1 dot (normally a floating-point numeric constant) is dual-valued magic when parsed as the indirect object of a use or require? Have to peek at what comes into VERSION.

if you can differentiate between a v-string and any other string by your above method, you should be able to determine whether or not you have a v-string, no?

I can easily enough decide if I have a v-string or a string of the form "1.2.3.4" as ASCII, provided it has at least one dot in the latter. That's my purpose: to allow either as the value of $VERSION.

—John

Comment on Re: Re^3: Distinguishing a v-string from something else Select or Download Code

Replies are listed 'Best First'.
Re^5: Distinguishing a v-string from something else by particle (Vicar) on Dec 10, 2002 at 11:53 UTC
i really hope you can get this going. the code on your pad looks like a fantastic start. i would suggest that if you do find a way to distinguish a v-string from anything else, you submit a patch to Scalar::Util. an isvstring sub would be very handy. ~Particle accelerates	[reply] [d/l]