Re: Version parsing confused by sub version {}

2007-11-17 Thread Eric Wilhelm
# from Andreas J. Koenig # on Saturday 17 November 2007 01:54: A different and slightly less brute fix would probably be to say version::-new() like I do on all package names always everywhere because it's the only safe way to call a method on a package name that has no colons in it. Well, or

Re: Version parsing confused by sub version {}

2007-11-17 Thread Andreas J. Koenig
On Sat, 17 Nov 2007 02:10:40 -0800, Eric Wilhelm [EMAIL PROTECTED] said: # from Andreas J. Koenig # on Saturday 17 November 2007 01:54: A different and slightly less brute fix would probably be to say version::-new() like I do on all package names always everywhere because it's the

Re: Version parsing confused by sub version {}

2007-11-17 Thread Adam Kennedy
Dear god that is evil. How the hell is doing that sort of stuff. Adam K On 17/11/2007, Michael G Schwern [EMAIL PROTECTED] wrote: A bug in MakeMaker's parse_version() was found recently. Module::Build has the same bug. https://rt.cpan.org/Ticket/Display.html?id=30747 It's reproducible

Version parsing confused by sub version {}

2007-11-16 Thread Michael G Schwern
A bug in MakeMaker's parse_version() was found recently. Module::Build has the same bug. https://rt.cpan.org/Ticket/Display.html?id=30747 It's reproducible by getting the version from a module like this: $VERSION = 1.23; sub version { $VERSION } and then this: use version; $VERSION =