Re: Testing print failures

2008-01-06 Thread Michael G Schwern
nadim khemir wrote: > As for the layers of neurosis, the only anxiety is the one created by your > own > delusions. I see only a test like an other. If we had infinite time and attention, yes. But we don't. And time spent checking the return value of print and writing a complicated test for if

Re: Testing print failures

2008-01-06 Thread Chris Dolan
On Jan 6, 2008, at 5:10 AM, Michael G Schwern wrote: nadim khemir wrote: As for the layers of neurosis, the only anxiety is the one created by your own delusions. I see only a test like an other. If we had infinite time and attention, yes. But we don't. And time spent checking the retur

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

Fixed Test::Builders "regexp" detection code.

2008-01-06 Thread demerphq
Just a heads up that I patched the core version of Test::Builder to use more reliable and robust methods for detecting regexps in test cases. This makes them robust to changes in the internals and also prevents Test::Builder from getting confused if someone uses blessed qr//'s. Cheers, yves -- p

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

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* cod

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 PRO

Re: Fixed Test::Builders "regexp" detection code.

2008-01-06 Thread Michael G Schwern
demerphq wrote: > Just a heads up that I patched the core version of Test::Builder to > use more reliable and robust methods for detecting regexps in test > cases. This makes them robust to changes in the internals and also > prevents Test::Builder from getting confused if someone uses blessed > qr

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