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
In reply to Re: Re^3: Distinguishing a v-string from something else
by John M. Dlugosz
in thread Distinguishing a v-string from something else
by John M. Dlugosz
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |