in reply to v-string warning in 5.8.0

as far as i know, v-strings made a brief entrance in perl 5.6, and broke all kinds of backwards compatibility. just forget vstrings, and simply 
require 5.6;

[download]
Of interest might also be Everything you wanted to know about Module Version Numbers and Checking

Replies are listed 'Best First'.
Re: Re: v-string warning in 5.8.0
by virtualsue (Vicar) on Jul 27, 2002 at 09:39 UTC
    This is what happens if I do a require 5.6; (or a use 5.6;): 
    Perl v5.600.0 required--this is only v5.6.1, stopped (did you mean v5.
+6.0?) at it line 4.
BEGIN failed--compilation aborted at it line 4.

    [download]
[reply]
[d/l]
[select]

      Okay! The answer to my question, as I see it from the responses, is as follows:

      1. v-string requires (i.e. require v5.6) are not a usable feature (they are backward combatible). Don't.
      2. Instead, either
        • require 5.006

          or

        • require 5.6.0

      Thank you all for your help!

      update: Everything you wanted to know about Module Version Numbers and Checking contains some more relevant info about v-strings and versioning.

[reply]

        require 5.6.0 is a v-string require. If it's got more then one decimal point, the "v" isn't required. (BTW, one of my favorite ways for somthing to break when you upgrade perl: In new versions of the autoconf package in debian, autoconf is a wrapper script to figure out what version of autoconf should be called. Using subs named v250 and v213, which new perls give a simple "syntax error" on. (BTW, my ++ goes to whoever can figure out exactly why this is a syntax error, and doesn't create and call ú() and Õ().)

        Confession: It does an Immortal Body good.

[reply]
[d/l]

In Section Seekers of Perl Wisdom