For example, if you get '1.0', that could have really been written '1.0', or 49.46.48. There's no way to tell, other then context.

i'm not so sure this is correct. the code below seems to illustrate the storage of v-strings is different than other text strings, as v-strings are stored as octals and periods are not included. \1 is not the same as chr(49).

> perl -MDevel::Peek -e"$a=v1.0; $b='1.0'; Dump$a; Dump$b"
SV = PV(0x182ebf4) at 0x182383c
  REFCNT = 1
  FLAGS = (POK,pPOK)
  PV = 0x182013c "\1\0"\0
  CUR = 2
  LEN = 3
SV = PV(0x182ec24) at 0x1823848
  REFCNT = 1
  FLAGS = (POK,pPOK)
  PV = 0x182012c "1.0"\0
  CUR = 3
  LEN = 4

[download]

~Particle *accelerates*

In reply to Re^2: Distinguishing a v-string from something else by particle
in thread Distinguishing a v-string from something else by John M. Dlugosz

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.