Skip Menu |

This queue is for tickets about the Module-Metadata CPAN distribution.

Maintainer(s)' notes

Attention bug reporters: issues MUST include the version of Module::Metadata that you are running that exhibit the stated symptoms. thank you!

Report information
The Basics
Id: 93054
Status: rejected
Priority: 0/
Queue: Module-Metadata

People
Owner: Nobody in particular
Requestors: ether [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Treatment of underscore versions inconsistent with version.pm
Consider the 0.98_05 release of Test::More: its code has: our $VERSION = '0.98_05'; $VERSION = eval $VERSION; Test::More->VERSION returns 0.9805, but Module::Metadata->new_...->version returns 0.98_05. This results in various comparisons failing, e.g. version.pm objects. (If modules with underscores *must* eval their $VERSION on the same line, so that Module::Metadata can take that into account, then we should fix all core modules that violate this, and think about ways of communicating this issue - metrics in Module::CPANTS::Analyse and perlcritic? Can we do something in PAUSE?)
Show quoted text
> our $VERSION = '0.98_05'; > $VERSION = eval $VERSION; > > Test::More->VERSION returns 0.9805, but Module::Metadata->new_...-
> >version returns 0.98_05. This results in various comparisons failing,
> e.g. version.pm objects.
But the eval fixes other version comparisons: use Test::More 0.98_05; # compiled as 0.9805 It's a hack to make the use line work with an alpha. The issue, as always, is knowing what questions are being asked and thus what semantics need to be considered.
I phrased this question in a boneheaded way, and we will be addressing underscore versions in version.pm anyway.