Re: Dev version numbers, warnings, XS and MakeMaker dont play nicely together.

# from demerphq
# on Sunday 06 January 2008 16:54:

>So we are told the way to mark a module as development is to use an
>underbar in the version number:
>
>$VERSION= "1.23_01";
>
>but this will produce warnings if you assert a required version
>number, as the version isn't numeric.

Does *any* code besides pause actually decide that "this is an alpha"?

I think that's the $dist =~ /\d\.\d+_\d/ bit around line 1474 in 
mldistwatch.  $dist = $self->{DIST} though and I'm getting lost in the 
BIGLOOP bit of checkfornew() as to whether that's looking at the 
extracted $VERSION, the META.yml $VERSION, or the bit in the filename.  
(Hmm, I guess line 1487's "$dist =~ /\.pm..." implies filename.)

So, if all of the alpha-y magic is just in the filename, what would 
happen if "make dist" had an "alpha" option which injected "TRIAL" into 
the filename?  Would that appropriately tickle the other half of that 
if() at line 1474?

Or a flag in META.yml?

Then we can do away with all of the underscores?

--Eric
-- 
perl -e 'srand; print join(" ",sort({rand() < 0.5}
  qw(sometimes it is important to be consistent)));'
---------------------------------------------------
    http://scratchcomputing.com
---------------------------------------------------