Phalanx / CPANTS / Kwalitee

2003-10-13 Thread Thomas Klausner
Hi! CPANTS and Phalanx both care about Kwalitee. So I thought it might be a good idea to come up with one more or less complete list of Kwalitee-hints that both projects can use. A lot of the hints listed at http://qa.perl.org/phalanx/kwalitee.html are rather vague, which is OK for Phalanx, as it

Re: Phalanx / CPANTS / Kwalitee

2003-10-13 Thread Michael G Schwern
On Mon, Oct 13, 2003 at 10:28:29AM +0200, Thomas Klausner wrote: > * contains files: > * Makefile.PL or Build.PL or configure configure? > * README Personally, I find READMEs useless duplication. Even more so now that search.cpan.org works so well. > * t/* or test.pl test.pl is not a go

Re: Phalanx / CPANTS / Kwalitee

2003-10-13 Thread Tels
-BEGIN PGP SIGNED MESSAGE- Moin, On Monday 13 October 2003 11:57, Michael G Schwern wrote: > On Mon, Oct 13, 2003 at 10:28:29AM +0200, Thomas Klausner wrote: > > * contains files: > > * Makefile.PL or Build.PL or configure > > configure? > > > * README > > Personally, I find READMEs u

Re: Phalanx / CPANTS / Kwalitee

2003-10-13 Thread Rafael Garcia-Suarez
Thomas Klausner wrote in perl.qa : > > Hints that were in Leon's last release, but which I didn't port up to now: > * POD errors > * POD/Code ratio (what would be a good measurement?) use Pod::Coverage ? > * testers results > * number of releases

Re: Phalanx / CPANTS / Kwalitee

2003-10-13 Thread Michael G Schwern
On Mon, Oct 13, 2003 at 06:51:43PM +0200, Tels wrote: > > > * t/* or test.pl > > > > test.pl is not a good thing. It doesn't get parsed by "make test". It > > just runs and spits the output to the screen. If a test fails, "make test" > > will still succeed. Still, its better than nothing at a

Devel::Cover bug in ActiveState Perl for *Linux*

2003-10-13 Thread Ovid
After much research, I've managed to reduce a Devel::Cover bug down to a one-liner which only fails on one box. This box is unique because it's ActiveState Perl for Linux (not my choice!). However, that might be a red herring. My 'perl -V' is below the test case. Does anyone have a similar s

Re: Phalanx / CPANTS / Kwalitee

2003-10-13 Thread Tels
-BEGIN PGP SIGNED MESSAGE- Moin, On Monday 13 October 2003 10:28, Thomas Klausner wrote: > Hi! > * POD/Code ratio (what would be a good measurement?) No. Some _very_ complex code takes little documentation like: =head2 sub delete_first_n_entries($N) Deletes the first N

Re: Devel::Cover bug in ActiveState Perl for *Linux*

2003-10-13 Thread Ovid
FYI: I've managed to replicate this error on another ActiveState Perl linux box. The Perl -V information is the same, but the module list is quite a bit smaller. The only common element that I can find is ActiveState. Cheers, Ovid = Silence is Evilhttp://users.easystreet.com/

Re: Devel::Cover bug in ActiveState Perl for *Linux*

2003-10-13 Thread Paul Johnson
On Mon, Oct 13, 2003 at 01:49:58PM -0700, Ovid wrote: > After much research, I've managed to reduce a Devel::Cover bug down to > a one-liner which only fails on one box. This box is unique because > it's ActiveState Perl for Linux (not my choice!). However, that might > be a red herring. My 'pe

Re: Devel::Cover bug in ActiveState Perl for *Linux*

2003-10-13 Thread Ovid
--- Paul Johnson <[EMAIL PROTECTED]> wrote: > I think the key is that it is perl version 5.6.1. I can reproduce the > problem on a stock 5.6.1 on linux (well, hacked just enough to get it to > build). Hmmm ... I saw this *after* my second ActiveState email. > Actually, I wonder whether 5.6.1 sho