On 4/19/10 7:51 AM, David Golden wrote:
On Mon, Apr 19, 2010 at 7:55 AM, Elliot Shank<p...@galumph.com>
wrote:
Oof. Version numbers: "All components after the first are
restricted to the range 0 to 999." That's going to be a problem
for those of us who include things like VCS revisions and CI build
numbers in version numbers.
You can do that as long as you use regular decimals and not
dotted-decimals.
Version numbers at work: v<manual>.<manual>.<Subversion revision>.<CI build
number>
The repository revision is currently six digits and some distribution build
numbers have reached four digits.
But if you ask version.pm to numify it, you get this:
I've dug though the version.pm source many times. (sigh) I'm grateful for
those of you who have tackled this nasty problem.
Now consider how version.pm converts those decimals back to dotted
form:
Well, don't do that. :] I consider numification to be a one-way trip.
CPAN Authors are free to use dotted decimals outside that range, but
any spec that contains them will be treated as invalid.
I'm not worried about CPAN authors, I'm worried about DarkPAN authors, i.e. me
in the above scenario. I'm primarily worried about toolchain support changing
in the future.
