Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I think this is a jolly good idea. The amount of additional mails module authors might get is nothing compared to the amount of time that could be saved by reports that are actually useful.

    Most reports are incomplete. They usually don't contain the version of perl or the version of the modules they used, or a combination thereof. We seldom get the actual output users receive from the broken programs, nor even the code they used. Establishing these information often takes one or two additional emails to the chap reporting the bug.

    Finally, it would allow formalizing the format of reports so that rules can be easily plugged into .procmailrc. More than once a report has been moved into my spam folder and I almost missed it (maybe I did even miss a few - how should I know?)

    Some things on your list of possible features will be tricky to do, though. I don't see how a list of prerequesite modules could be created if the initial Makefile.PL no longer exists or is buried somewhere deep down in the root's home directory. If I understand you correctly, this perlmodbug tool should not just be used when installing a module but also when discovering a bug later while using it.