X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2Fversion.pm;h=520c781a8f4421dcf1107adb09cdecc311852349;hb=cc83745da206d409d7227df077f422fd9ecbe680;hp=63d25acad7f6e4cd4c53c0e7e8d1d3064ddefeee;hpb=a7ad731c5ef0d5f23c440149f8f810a4785a2903;p=p5sagit%2Fp5-mst-13.2.git diff --git a/lib/version.pm b/lib/version.pm index 63d25ac..520c781 100644 --- a/lib/version.pm +++ b/lib/version.pm @@ -1,4 +1,4 @@ -#!/usr/local/bin/perl -w +#!perl -w package version; use 5.005_03; @@ -9,10 +9,11 @@ use vars qw(@ISA $VERSION $CLASS); @ISA = qw(DynaLoader); -$VERSION = (qw$Revision: 2.1 $)[1]/10; +$VERSION = 0.29; # stop using CVS and switch to subversion $CLASS = 'version'; +local $^W; # shut up the 'redefined' warning for UNIVERSAL::VERSION bootstrap version if $] < 5.009; # Preloaded methods go here. @@ -30,21 +31,22 @@ version - Perl extension for Version Objects $version = new version "12.2.1"; # must be quoted! print $version; # 12.2.1 print $version->numify; # 12.002001 - if ( $version > 12.2 ) # true + if ( $version gt "v12.2" ) # true $vstring = new version qw(v1.2); # must be quoted! print $vstring; # 1.2 - $betaver = new version "1.2_3"; # must be quoted! - print $betaver; # 1.2_3 + $alphaver = new version "1.2_3"; # must be quoted! + print $alphaver; # 1.2_3 + print $alphaver->is_alpha(); # true - $perlver = new version "5.005_03"; # must be quoted! + $perlver = new version 5.005_03; # must not be quoted! print $perlver; # 5.5.30 =head1 DESCRIPTION Overloaded version objects for all versions of Perl. This module -implments all of the features of version objects which will be part +implements all of the features of version objects which will be part of Perl 5.10.0 except automatic v-string handling. See L<"Quoting">. =head2 What IS a version @@ -55,284 +57,173 @@ single underscore. This corresponds to what Perl itself uses for a version, as well as extending the "version as number" that is discussed in the various editions of the Camel book. -=head2 Object Methods - -Overloading has been used with version objects to provide a natural -interface for their use. All mathematical operations are forbidden, -since they don't make any sense for versions. For the subsequent -examples, the following two objects will be used: - - $ver = new version "1.2.3"; # see "Quoting" below - $beta = new version "1.2_3"; # see "Beta versions" below - -=item * Stringification - Any time a version object is used as a string, -a stringified representation is returned in reduced form (no extraneous -zeros): - - print $ver->stringify; # prints 1.2.3 - print $ver; # same thing - -=item * Numification - although all mathematical operations on version -objects are forbidden by default, it is possible to retrieve a number -which roughly corresponds to the version object through the use of the -$obj->numify method. For formatting purposes, when displaying a number -which corresponds a version object, all sub versions are assumed to have -three decimal places. So for example: - - print $ver->numify; # prints 1.002003 - -=item * Comparison operators - Both cmp and <=> operators perform the -same comparison between terms (upgrading to a version object -automatically). Perl automatically generates all of the other comparison -operators based on those two. For example, the following relations hold: - - As Number As String Truth Value - --------- ------------ ----------- - $ver > 1.0 $ver gt "1.0" true - $ver < 2.5 $ver lt true - $ver != 1.3 $ver ne "1.3" true - $ver == 1.2 $ver eq "1.2" false - $ver == 1.2.3 $ver eq "1.2.3" see discussion below - $ver == v1.2.3 $ver eq "v1.2.3" ditto - -In versions of Perl prior to the 5.9.0 development releases, it is not -permitted to use bare v-strings in either form, due to the nature of Perl's -parsing operation. After that version (and in the stable 5.10.0 release), -v-strings can be used with version objects without problem, see L<"Quoting"> -for more discussion of this topic. In the case of the last two lines of -the table above, only the string comparison will be true; the numerical -comparison will test false. However, you can do this: - - $ver == "1.2.3" or $ver = "v.1.2.3" # both true - -even though you are doing a "numeric" comparison with a "string" value. -It is probably best to chose either the numeric notation or the string -notation and stick with it, to reduce confusion. See also L<"Quoting">. - -=head2 Quoting - -Because of the nature of the Perl parsing and tokenizing routines, -you should always quote the parameter to the new() operator/method. The -exact notation is vitally important to correctly determine the version -that is requested. You don't B to quote the version parameter, -but you should be aware of what Perl is likely to do in those cases. - -If you use a mathematic formula that resolves to a floating point number, -you are dependent on Perl's conversion routines to yield the version you -expect. You are pretty safe by dividing by a power of 10, for example, -but other operations are not likely to be what you intend. For example: - - $VERSION = new version (qw$Revision: 1.4)[1]/10; - print $VERSION; # yields 0.14 - $V2 = new version 100/9; # Integer overflow in decimal number - print $V2; # yields 11_1285418553 - -You B use a bare number, if you only have a major and minor version, -since this should never in practice yield a floating point notation -error. For example: - - $VERSION = new version 10.2; # almost certainly ok - $VERSION = new version "10.2"; # guaranteed ok - -Perl 5.9.0 and beyond will be able to automatically quote v-strings -(which may become the recommended notation), but that is not possible in -earlier versions of Perl. In other words: - - $version = new version "v2.5.4"; # legal in all versions of Perl - $newvers = new version v2.5.4; # legal only in Perl > 5.9.0 - - -=head2 Types of Versions Objects - -There are three basic types of Version Objects: - -=item * Ordinary versions - These are the versions that normal -modules will use. Can contain as many subversions as required. -In particular, those using RCS/CVS can use one of the following: - - $VERSION = new version (qw$Revision: 2.1 $)[1]; # all Perls - $VERSION = new version qw$Revision: 2.1 $[1]; # Perl >= 5.6.0 - -and the current RCS Revision for that file will be inserted -automatically. If the file has been moved to a branch, the -Revision will have three or more elements; otherwise, it will -have only two. This allows you to automatically increment -your module version by using the Revision number from the primary -file in a distribution, see L. - -In order to be compatible with earlier Perl version styles, any use -of versions of the form 5.006001 will be translated as 5.6.1, In -other words a version with a single decimal place will be parsed -as implicitely having three places between subversion. - -=item * Beta versions - For module authors using CPAN, the -convention has been to note unstable releases with an underscore -in the version string, see L. Beta releases will test as being -newer than the more recent stable release, and less than the next -stable release. For example: - - $betaver = new version "12.3_1"; # must quote - -obeys the relationship - - 12.3 < $betaver < 12.4 - -As a matter of fact, if is also true that +There are actually two distinct ways to initialize versions: - 12.3.0 < $betaver < 12.3.1 +=over 4 -where the subversion is identical but the beta release is less than -the non-beta release. +=item * Numeric Versions -=item * Perl-style versions - an exceptional case is versions that -were only used by Perl releases prior to 5.6.0. If a version -string contains an underscore immediately followed by a zero followed -by a non-zero number, the version is processed according to the rules -described in L -released with Perl 5.6.0. As an example: +Any initial parameter which "looks like a number", see L. - $perlver = new version "5.005_03"; +=item * V-String Versions -is interpreted, not as a beta release, but as the version 5.5.30, NOTE -that the major and minor versions are unchanged but the subversion is -multiplied by 10, since the above was implicitely read as 5.005.030. -There are modules currently on CPAN which may fall under of this rule, so -module authors are urged to pay close attention to what version they are -specifying. +Any initial parameter which contains more than one decimal point, +contains an embedded underscore, or has a leading 'v' see L. -=head2 Replacement UNIVERSAL::VERSION +=back -In addition to the version objects, this modules also replaces the core -UNIVERSAL::VERSION function with one that uses version objects for its -comparisons. So, for example, with all existing versions of Perl, -something like the following pseudocode would fail: +Both of these methods will produce similar version objects, in that +the default stringification will always be in a reduced form, i.e.: - package vertest; - $VERSION = 0.45; + $v = new version 1.002003; # 1.2.3 + $v2 = new version "1.2.3"; # 1.2.3 + $v3 = new version v1.2.3; # 1.2.3 for Perl > v5.8.0 + $v4 = new version 1.2.3; # 1.2.3 for Perl > v5.8.0 - package main; - use vertest 0.5; +Please see L<"Quoting"> for more details on how Perl will parse various +input values. -even though those versions are meant to be read as 0.045 and 0.005 -respectively. The UNIVERSAL::VERSION replacement function included -with this module changes that behavior so that it will B fail. +Any value passed to the new() operator will be parsed only so far as it +contains a numeric, decimal, or underscore character. So, for example: -=head1 EXPORT + $v1 = new version "99 and 94/100 percent pure"; # $v1 == 99.0 + $v2 = new version "something"; # $v2 == "" and $v2->numify == 0 -None by default. - -=head1 AUTHOR +However, see L for one case where non-numeric text is +acceptable when initializing version objects. -John Peacock Ejpeacock@rowman.comE +=head2 Numeric Versions -=head1 SEE ALSO +These correspond to historical versions of Perl itself prior to v5.6.0, +as well as all other modules which follow the Camel rules for the +$VERSION scalar. A numeric version is initialized with what looks like +a floating point number. Leading zeros B significant and trailing +zeros are implied so that a minimum of three places is maintained +between subversions. What this means is that any subversion (digits +to the right of the decimal place) that contains less than three digits +will have trailing zeros added to make up the difference. For example: -L. + $v = new version 1.2; # 1.200 + $v = new version 1.02; # 1.20 + $v = new version 1.002; # 1.2 + $v = new version 1.0023; # 1.2.300 + $v = new version 1.00203; # 1.2.30 + $v = new version 1.002_03; # 1.2.30 See L<"Quoting"> + $v = new version 1.002003; # 1.2.3 -=cut -#!/usr/local/bin/perl -w -package version; +All of the preceeding examples except the second to last are true +whether or not the input value is quoted. The important feature is that +the input value contains only a single decimal. -use 5.005_03; -use strict; +=head2 V-String Versions -require Exporter; -require DynaLoader; -use vars qw(@ISA %EXPORT_TAGS @EXPORT_OK @EXPORT $VERSION $CLASS); +These are the newest form of versions, and correspond to Perl's own +version style beginning with v5.6.0. Starting with Perl v5.10.0, +this is likely to be the preferred form. This method requires that +the input parameter be quoted, although Perl > v5.9.0 can use bare +v-strings as a special form of quoting. -@ISA = qw(Exporter DynaLoader); +Unlike L, V-String Versions must either have more than +a single decimal point, e.g. "5.6.1" B must be prefaced by a "v" +like this "v5.6" (much like v-string notation). In fact, with the +newest Perl v-strings themselves can be used to initialize version +objects. Also unlike L, leading zeros are B +significant, and trailing zeros must be explicitely specified (i.e. +will not be automatically added). In addition, the subversions are +not enforced to be three decimal places. -# This allows declaration use version ':all'; -# If you do not need this, moving things directly into @EXPORT or @EXPORT_OK -# will save memory. -%EXPORT_TAGS = ( 'all' => [ qw( +So, for example: -) ] ); + $v = new version "v1.2"; # 1.2 + $v = new version "v1.002"; # 1.2 + $v = new version "1.2.3"; # 1.2.3 + $v = new version "v1.2.3"; # 1.2.3 + $v = new version "v1.0003"; # 1.3 -@EXPORT_OK = ( @{ $EXPORT_TAGS{'all'} } ); +In additional to conventional versions, V-String Versions can be +used to create L. -@EXPORT = qw( -); +In general, V-String Versions permit the greatest amount of freedom +to specify a version, whereas Numeric Versions enforce a certain +uniformity. See also L for an additional method of +initializing version objects. -$VERSION = (qw$Revision: 1.8 $)[1]/10; +=head2 Object Methods -$CLASS = 'version'; +Overloading has been used with version objects to provide a natural +interface for their use. All mathematical operations are forbidden, +since they don't make any sense for base version objects. -bootstrap version if $] < 5.009; +=over 4 -# Preloaded methods go here. +=item * New Operator -1; -__END__ +Like all OO interfaces, the new() operator is used to initialize +version objects. One way to increment versions when programming is to +use the CVS variable $Revision, which is automatically incremented by +CVS every time the file is committed to the repository. -=head1 NAME +=back -version - Perl extension for Version Objects +In order to facilitate this feature, the following +code can be employed: -=head1 SYNOPSIS + $VERSION = new version qw$Revision: 2.7 $; - use version; - $version = new version "12.2.1"; # must be quoted! - print $version; # 12.2.1 - print $version->numify; # 12.002001 - if ( $version > 12.2 ) # true +and the version object will be created as if the following code +were used: - $vstring = new version qw(v1.2); # must be quoted! - print $vstring; # 1.2 + $VERSION = new version "v2.7"; - $betaver = new version "1.2_3"; # must be quoted! - print $betaver; # 1.2_3 +In other words, the version will be automatically parsed out of the +string, and it will be quoted to preserve the meaning CVS normally +carries for versions. - $perlver = new version "5.005_03"; # must be quoted! - print $perlver; # 5.5.30 +For the subsequent examples, the following two objects will be used: -=head1 DESCRIPTION - -Overloaded version objects for all versions of Perl. This module -implments all of the features of version objects which will be part -of Perl 5.10.0 except automatic v-string handling. See L<"Quoting">. - -=head2 What IS a version - -For the purposes of this module, a version "number" is a sequence of -positive integral values separated by decimal points and optionally a -single underscore. This corresponds to what Perl itself uses for a -version, as well as including the "version as number" that is discussed -in the various editions of the Camel book. + $ver = new version "1.2.3"; # see "Quoting" below + $alpha = new version "1.2_3"; # see "Alpha versions" below -=head2 Object Methods +=over 4 -Overloading has been used with version objects to provide a natural -interface for their use. All mathematical operations are forbidden, -since they don't make any sense for versions. For the subsequent -examples, the following two objects will be used: +=item * Stringification - $ver = new version "1.2.3"; # see "Quoting" below - $beta = new version "1.2_3"; # see "Beta versions" below +Any time a version object is used as a string, a stringified +representation is returned in reduced form (no extraneous zeros): -=item * Stringification - Any time a version object is used as a string, -a stringified representation is returned in reduced form (no extraneous -zeros): +=back print $ver->stringify; # prints 1.2.3 print $ver; # same thing -=item * Numification - although all mathematical operations on version -objects are forbidden by default, it is possible to retrieve a number -which roughly corresponds to the version object through the use of the -$obj->numify method. For formatting purposes, when displaying a number -which corresponds a version object, all sub versions are assumed to have +=over 4 + +=item * Numification + +Although all mathematical operations on version objects are forbidden +by default, it is possible to retrieve a number which roughly +corresponds to the version object through the use of the $obj->numify +method. For formatting purposes, when displaying a number which +corresponds a version object, all sub versions are assumed to have three decimal places. So for example: print $ver->numify; # prints 1.002003 -=item * Comparison operators - Both cmp and <=> operators perform the -same comparison between terms (upgrading to a version object -automatically). Perl automatically generates all of the other comparison -operators based on those two. For example, the following relations hold: +=item * Comparison operators - As Number As String Truth Value - --------- ------------ ----------- +Both cmp and <=> operators perform the same comparison between terms +(upgrading to a version object automatically). Perl automatically +generates all of the other comparison operators based on those two. +In addition to the obvious equalities listed below, appending a single +trailing 0 term does not change the value of a version for comparison +purposes. In other words "v1.2" and "v1.2.0" are identical versions. + +For example, the following relations hold: + + As Number As String Truth Value + --------- ------------ ----------- $ver > 1.0 $ver gt "1.0" true $ver < 2.5 $ver lt true $ver != 1.3 $ver ne "1.3" true @@ -344,23 +235,55 @@ In versions of Perl prior to the 5.9.0 development releases, it is not permitted to use bare v-strings in either form, due to the nature of Perl's parsing operation. After that version (and in the stable 5.10.0 release), v-strings can be used with version objects without problem, see L<"Quoting"> -for more discussion of this topic. In the case of the last two lines of +for more discussion of this topic. In the case of the last two lines of the table above, only the string comparison will be true; the numerical comparison will test false. However, you can do this: - $ver == "1.2.3" or $ver = "v.1.2.3" # both true + $ver == "1.2.3" or $ver == "v1.2.3" # both true even though you are doing a "numeric" comparison with a "string" value. -It is probably best to chose either the numeric notation or the string +It is probably best to chose either the numeric notation or the string notation and stick with it, to reduce confusion. See also L<"Quoting">. +=item * Logical Operators + +If you need to test whether a version object +has been initialized, you can simply test it directly: + + $vobj = new version $something; + if ( $vobj ) # true only if $something was non-blank + +You can also test whether a version object is a L, for +example to prevent the use of some feature not present in the main +release: + + $vobj = new version "1.2_3"; # MUST QUOTE + ...later... + if ( $vobj->is_alpha ) # True + +=back + =head2 Quoting -Because of the nature of the Perl parsing and tokenizing routines, -you should always quote the parameter to the new() operator/method. The -exact notation is vitally important to correctly determine the version -that is requested. You don't B to quote the version parameter, -but you should be aware of what Perl is likely to do in those cases. +Because of the nature of the Perl parsing and tokenizing routines, +certain initialization values B be quoted in order to correctly +parse as the intended version, and additionally, some initial values +B be quoted to obtain the intended version. + +Except for L, any version initialized with something +that looks like a number (a single decimal place) will be parsed in +the same way whether or not the term is quoted. In order to be +compatible with earlier Perl version styles, any use of versions of +the form 5.006001 will be translated as 5.6.1. In other words, a +version with a single decimal place will be parsed as implicitly +having three places between subversions. + +The complicating factor is that in bare numbers (i.e. unquoted), the +underscore is a legal numeric character and is automatically stripped +by the Perl tokenizer before the version code is called. However, if +a number containing a single decimal and an underscore is quoted, i.e. +not bare, that is considered a L and the underscore is +significant. If you use a mathematic formula that resolves to a floating point number, you are dependent on Perl's conversion routines to yield the version you @@ -372,13 +295,6 @@ but other operations are not likely to be what you intend. For example: $V2 = new version 100/9; # Integer overflow in decimal number print $V2; # yields 11_1285418553 -You B use a bare number, if you only have a major and minor version, -since this should never in practice yield a floating point notation -error. For example: - - $VERSION = new version 10.2; # almost certainly ok - $VERSION = new version "10.2"; # guaranteed ok - Perl 5.9.0 and beyond will be able to automatically quote v-strings (which may become the recommended notation), but that is not possible in earlier versions of Perl. In other words: @@ -389,73 +305,50 @@ earlier versions of Perl. In other words: =head2 Types of Versions Objects -There are three basic types of Version Objects: +There are two types of Version Objects: -=item * Ordinary versions - These are the versions that normal -modules will use. Can contain as many subversions as required. -In particular, those using RCS/CVS can use one of the following: +=over 4 - $VERSION = new version (qw$Revision: 1.8 $)[1]; # all Perls - $VERSION = new version qw$Revision: 1.8 $[1]; # Perl >= 5.6.0 +=item * Ordinary versions -and the current RCS Revision for that file will be inserted -automatically. If the file has been moved to a branch, the -Revision will have three or more elements; otherwise, it will -have only two. This allows you to automatically increment -your module version by using the Revision number from the primary -file in a distribution, see L. +These are the versions that normal modules will use. Can contain as +many subversions as required. In particular, those using RCS/CVS can +use one of the following: -=item * Beta versions - For module authors using CPAN, the -convention has been to note unstable releases with an underscore -in the version string, see L. Beta releases will test as being -newer than the more recent stable release, and less than the next -stable release. For example: + $VERSION = new version qw$Revision: 2.7 $; - $betaver = new version "12.3_1"; # must quote +and the current RCS Revision for that file will be inserted +automatically. If the file has been moved to a branch, the Revision +will have three or more elements; otherwise, it will have only two. +This allows you to automatically increment your module version by +using the Revision number from the primary file in a distribution, see +L. -obeys the relationship +=item * alpha versions - 12.3 < $betaver < 12.4 +For module authors using CPAN, the convention has been to note +unstable releases with an underscore in the version string, see +L. Alpha releases will test as being newer than the more recent +stable release, and less than the next stable release. For example: -As a matter of fact, if is also true that + $alphaver = new version "12.3_1"; # must quote - 12.3.0 < $betaver < 12.3.1 +obeys the relationship -where the subversion is identical but the beta release is less than -the non-beta release. + 12.3 < $alphaver < 12.4 -=item * Perl-style versions - an exceptional case is versions that -were only used by Perl releases prior to 5.6.0. If a version -string contains an underscore immediately followed by a zero followed -by a non-zero number, the version is processed according to the rules -described in L -released with Perl 5.6.0. As an example: +As a matter of fact, if is also true that - $perlver = new version "5.005_03"; + 12.3.0 < $alphaver < 12.3.1 -is interpreted, not as a beta release, but as the version 5.5.30, NOTE -that the major and minor versions are unchanged but the subversion is -multiplied by 10, since the above was implicitely read as 5.005.030. -There are modules currently on CPAN which may fall under of this rule, so -module authors are urged to pay close attention to what version they are -specifying. +where the subversion is identical but the alpha release is less than +the non-alpha release. =head2 Replacement UNIVERSAL::VERSION In addition to the version objects, this modules also replaces the core UNIVERSAL::VERSION function with one that uses version objects for its -comparisons. So, for example, with all existing versions of Perl, -something like the following pseudocode would fail: - - package vertest; - $VERSION = 0.45; - - package main; - use vertest 0.5; - -even though those versions are meant to be read as 0.045 and 0.005 -respectively. The UNIVERSAL::VERSION replacement function included -with this module changes that behavior so that it will B fail. +comparisons. =head1 EXPORT