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

2008-01-07 Thread demerphq
On 07/01/2008, Yitzchak Scott-Thoennes [EMAIL PROTECTED] wrote: On Sun, January 6, 2008 4:54 pm, demerphq wrote: 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

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

2008-01-07 Thread John Peacock
Zefram wrote: demerphq wrote: $VERSION= 1.23_01; I've not seen that form, but $VERSION = 1.23_01; which of course doesn't put the underscore in the string value. This still delimits the subrevision portion, but without forcing anything else to handle the delimiter. Plus it

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

2008-01-07 Thread John Peacock
demerphq wrote: $VERSION = 1.12_01; $XS_VERSION = $VERSION; # only needed if you have XS code $VERSION = eval $VERSION; im not convinced this actually does anything. ISTR i had to roll my own parse out the $XS_VERSION code thingee for DDS. I;m very onfident that the recommended

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

2008-01-06 Thread demerphq
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. So the standard response is to do $VERSION= eval $VERSION; on the next

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

2008-01-06 Thread Zefram
demerphq wrote: $VERSION= 1.23_01; I've not seen that form, but $VERSION = 1.23_01; which of course doesn't put the underscore in the string value. This still delimits the subrevision portion, but without forcing anything else to handle the delimiter. but this will produce warnings if

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

2008-01-06 Thread Eric Wilhelm
# 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

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

2008-01-06 Thread Michael G Schwern
demerphq wrote: 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. We talked about this recently on [EMAIL PROTECTED]

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

2008-01-06 Thread Yitzchak Scott-Thoennes
On Sun, January 6, 2008 4:54 pm, demerphq wrote: 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. So the standard