Well... there's Zanas, which has

file.html.pm
-------
<html></html>
-------

And don't get me started on

file.gif.pm
------------------
(binary gif file)
------------------

Still haven't worked out what the hell they are for... :)

It's partly my fault for making the "what is a module" regex wrong.

Paper::Specs has used a code generator that doesn't escape properly, so half a dozen Paper::Specs::Avery::8XXX label modules die

description => "Avery 5 1/2" blah blah labels",

Of the ones that are my fault, we have gems like

tr [\$|\%|\&|\*] //g;

And one that got fixed...

$|=1;$::|=1;

Or Damian's use of @0   <-- that's a zero

Or the fact that <<1HERE1 is illegal per the docs, but does actually work.

Since it takes 4 or 5 minutes to nail down the exact fault location for each file, I haven't had time to get details on the rest, but it's mostly insanely ugly quote/regexs or fairly insane code in general that is causing the problems now, and I never said I'd support every single thing.

I've been uploading some autogenerated reports as well, to

http://ali.as/PPI/tinderbox/

So you can see there are a large number of modules uploaded with corrupted tarballs, or who have started using Build.PL without keeping the wrapper Makefile.PL for compatibility.

Adam

Rob Kinyon wrote:
I'm curious - what bugs in what modules are causing you fits?

Rob


On Wed, 19 Jan 2005 03:38:50 +1100, Adam Kennedy <[EMAIL PROTECTED]> wrote:

For those that are interested, PPI 0.900 just got uploaded.

This is a Beta 1 release. For the record, of the 38,000 non-Acme perl
modules in CPAN, PPI comfortably handles all but 20. (and 10 of those
are bugs in the modules)

It is now feature-complete and largely frozen, so if people were
interesting in having a bit of a dicker with PPI, from now on you should
be able to do so with a fairly reasonable assumption the API won't
change underneath you :)

Enjoy

Adam K

Adam Kennedy wrote:

Of course, if anyone is interested in helping, there are about a
zillion unit tests that need to be written...


I will help out on that. Which module is most finished?


"module" is a tricky word :)

http://search.cpan.org/~adamk/PPI-0.840/lib/PPI/Manual.pod#PPI_Data_Class_Full_Listing


As you can see from that URL, there are a *cough* LOT of modules in the Perl Document Object Model. (like pretty much every other object model)

There are two or three tasks where people can help if they like

Firstly, I'm currently trying to finish up a sort of "PPI CPAN
Tinderbox". A module (PPI::Tinderbox) that will pull down all of CPAN,
suck out the perl modules and run them all through a series of stress
tests.

Once this is working, I'll need people to help go through the logs, and
help find and isolate bugs (Tokenizer bugs, Lexer bugs, things being
recognised wrong, circular reference leaks, etc etc).

You should be fairly easily be able to install that module, and
configure some values in a 10 line launcher script. After it runs for
half a day or so and spits out the results, you can hunt stuff down.

PPI::Tester, the (broken till I sync it with 0.840) WxWindows-based
utility that shows the PDOM-dump for any code interactively as you type
it, should make this a lot easier.

Then just submit the code snippits to rt.cpan.org, I can do what needs
to be done to fix them much easier if others can help find them.

Second, there a zillion classes that need unit tests... but that's
pretty boring work :)

And third, well I need a tutorial. If someone wants to have a play
around with PPI in it's current state, which should be reasonably
stable, and then can write about their experiences, it's all fodder for
the POD-mill.

And fourth, if anyone REALLY wants to do unit testing, make a test
script for each of the documented PPI::Statement classes, generate some
simple Documents in it and make sure that the various methods in the
Statement classes generate what you expect them to.

Adam

_______________________________________________
sw-design mailing list
[email protected]
http://metaperl.com/cgi-bin/mailman/listinfo/sw-design

_______________________________________________ sw-design mailing list [email protected] http://metaperl.com/cgi-bin/mailman/listinfo/sw-design



_______________________________________________
sw-design mailing list
[email protected]
http://metaperl.com/cgi-bin/mailman/listinfo/sw-design

_______________________________________________ sw-design mailing list [email protected] http://metaperl.com/cgi-bin/mailman/listinfo/sw-design

Reply via email to