# from John Peacock
# on Sunday 19 April 2009 03:41:
>However, using $version->stringify() instead would be better than
> having META.yml contain an object dump for $VERSION. The version.pm
> object is guaranteed to stringify to the same form as was original
> present in the source file, which is the _only_ way to preserve the
> author's intention.
We already do this. In fact, this was Jonathan's complaint at the start
of this thread.
> Since most of the toolchain treats $VERSION as
> an atomic THING, and the few places which try to compare one $VERSION
> to another are already wired up with version.pm, this will work as
> any sane person would expect it to...
I'm fine with the current behavior, but the spec needs to be clarified.
What's the canonical handling? Is it 'version->new($meta->{version})'?
http://module-build.sourceforge.net/META-spec-current.html#version_specifications
If META.yml is used for Perl modules, it is reasonable to say that
versions must be stringified and compared ala version.pm. If META.yml
is for something beyond Perl modules then I'm in over my pay grade.
I can't see numify becoming the spec without causing trouble and I don't
see the benefit.
--Eric
--
The only thing that could save UNIX at this late date would be a new $30
shareware version that runs on an unexpanded Commodore 64.
--Don Lancaster (1991)
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
