Perl client $VERSION should be numeric
Brad Fitzpatrick
brad@danga.com
Thu, 1 Apr 2004 11:36:21 -0800 (PST)
Noted.
Version in CVS is now 1.13-pre.
On Wed, 31 Mar 2004, Jamie McCarthy wrote:
> The version number for the latest Cache::Memcached is 1.0.12. For
> the next release, it should be set to 1.13.
>
> perldoc perlmodlib:
>
> o Give the module a version/issue/release number.
>
> To be fully compatible with the Exporter and
> MakeMaker modules you should store your module's
> version number in a non-my package variable called
> $VERSION. This should be a floating point number
> with at least two digits after the decimal (i.e.,
> hundredths, e.g, "$VERSION = "0.01""). Don't use a
> "1.3.2" style version.
>
> perldoc perlstyle:
>
> The most common CPAN version numbering scheme looks like this:
>
> 1.00, 1.10, 1.11, 1.20, 1.30, 1.31, 1.32
>
> A correct CPAN version number is a floating point number
> with at least 2 digits after the decimal. You can test
> whether it conforms to CPAN by using
>
> perl -MExtUtils::MakeMaker -le 'print MM->parse_version(shift)' 'Foo.pm'
>
> If you want to release a 'beta' or 'alpha' version of a
> module but don't want CPAN.pm to list it as most recent use
> an '_' after the regular version number followed by at
> least 2 digits, eg. 1.20_01.
>
> perldoc Exporter:
>
> Since the default require_version method treats the
> $VERSION number as a simple numeric value it will regard
> version 1.10 as lower than 1.9. For this reason it is
> strongly recommended that you use numbers with at least two
> decimal places, e.g., 1.09.
>
> The symptom right now is that if you have 1.0.11 or any previous
> 1.0 version of Cache::Memcached installed, CPAN will report that
> it is already up to date, and refuse to install without a "force,"
> since:
>
> $ perl -le 'print "1.0.11" == "1.0.12"'
> 1
> --
> Jamie McCarthy
> http://mccarthy.vg/
> jamie@mccarthy.vg
>
>