David Golden <[email protected]> writes:
> On Fri, Jan 4, 2013 at 8:28 AM, Gabor Szabo <[email protected]> wrote:
>> I am not sure what does that mean. Is the version number comparison in
>> CPAN::Reporter
>> broken or should Module-Packaged declare Sort::Versions 1.5 as prerequisite?
>
> CPAN::Reporter uses CPAN::Version for version comparisions. (I wish
> we could use version.pm, but we are trying to be backwards compatible
> and not force older perls to have version.pm installed.)
>
> So whatever it's doing for version comparison in CPAN::Version::vcmp()
> is to blame. When I see 1.50 != 1.5, I immediately start thinking
> about floating point issues. Was this a 64 bit machine by any chance?
I don't think so. I believe this is even intentional.
% perl -MCPAN::Version -le 'print CPAN::Version->vcmp("1.5", "1.50")'
-1
When I see in the t/10version.t file:
1.57_00 1.57 1
1.5700 1.57 1
then I believe this was fully intentional. version.pm and CPAN::Version
are not compatible. Period. I was intending to switch to version.pm some
day but I'm more concerned about stability than compatibility. Version
numbers are still not boring enough. Sigh.
--
andreas
