Adam Kennedy wrote:
> It might be worth running Perl::MinimumVersion over the codebase real
> quick.
>
> It has all the obvious stuff coded into it (like warnings and qr//)
> already.
Swanky!
Some minor nits (-v not documented, documented output not the same as actual
output). And I can think
Gabor Szabo wrote:
> During perl Makefile.PL I am going to read the installed version of some C
> header files. I would like this information to be included in the test
> report.
>
> What is the correct way to do this ?
> Just print to STDOUT or to STDERR?
STDERR
Chris Dolan wrote:
>> token description { <-[#\n]>+ }
>
> The description can't start with a number if there is a test number:
isn't?
> token description { <-[#\n\d]> <-[#\n]>* }
On Thu, Sep 14, 2006 at 09:28:19PM -0400, Michael G Schwern wrote:
> Ovid wrote:
> > Also, for purposes of backwards compatability, I'm concerned about qr// and
> > $code->().
> > When were those first introduced in Perl? I don't want someone using
> > really old versions to not be able to use
On Thu, Sep 14, 2006 at 09:28:19PM -0400, Michael G Schwern wrote:
> Ovid wrote:
> > Also, for purposes of backwards compatability, I'm concerned about qr//
> > and $code->(). When were those first introduced in Perl? I don't want
> > someone using really old versions to not be able to use this c
During perl Makefile.PL I am going to read the installed version of some C
header files. I would like this information to be included in the test report.
What is the correct way to do this ?
Just print to STDOUT or to STDERR?
Gabor
