Yitzchak Scott-Thoennes [[EMAIL PROTECTED]] quoth: *> *>I thought the alpha/beta distinction was only relevant when there was a *>earlier GA release (so CPAN.pm doesn't upgrade 1.01 to 1.01_01 or some *>such.) Nevertheless, $VERSION should always be a number so that required *>version numbers work without extraneous warnings: *> *>~ $perl -we'use Date::Roman 1.0' *>Argument "1.0.1" isn't numeric in subroutine entry at -e line 1.
1.0 is also an invalid version number as it is defined as a floating point number with at least 2 digits following the decimal. *>Same thing happens with $VERSION="1.00_01" though, and MakeMaker (e.g. *>make dist's tarball name) loses the _ if you only say $VERSION=1.00_01; Not with my makemaker...at least not with 5.005_03 or 5.6.1. The "_nn" has been the semantic for denoting a beta for a long time so MM not dealing with it would be a surprise. *>Extensive discussion of this problem occured on perl5-porters in Feb *>and Mar under subjects '$VERSION problem', 'UNIVERSAL::version objects', *>and 'Argument "1.23_45" isn't numeric in subroutine entry'. This is a different problem and isn't terribly critical since it's for alpha/beta modules and shouldn't keep people from using version numbers properly. Much of CPAN is bereft of version numbers or valid numbers at all so I don't think it's a real sticking point. e.
