John Peacock wrote: > version-0.7203 now returns the same string that was used to initialize a > version object as the default stringification. The internal representa- > tion is no longer overtly visible (though you can get it via ->numify or > ->normal).
Well, that's only with version-0.7203+, right? It will be a while before I
can take that as a given on most systems.
> The one time that the string input isn't equal to the string output is
> qv() without a leading 'v' and only one decimal place, which appears to
> be the case here:
>
> use version; our $VERSION = qv('2.004');
>
> qv() is not a generic-version-object-creation function; it forces the
> extended version interpretation.
I am aware of that. That's one of the reasons why I chose to use it.
There have been point-point releases of Mail::SPF such as 2.000.1, and I
wanted to use a syntax that would work with both them and mere point
releases.
> The above should be either of:
>
> use version; our $VERSION = version->new('2.004');
> use version; our $VERSION = qv('v2.4.0');
>
> with the former probably more appropriate in this case (since that
> matches what CPAN thinks the $VERSION is)...
But doesn't `perldoc version` say that I am "strongly encouraged to use the
qv() operator" if I wanted to use extended versions? Does that recommen-
dation perhaps need to be further qualified then?
Julian.
pgp0qhVf5gMDh.pgp
Description: PGP signature
