wumpus has asked for the wisdom of the Perl Monks concerning the following question:
So I took the perldiag 5.8.8 manpage and made a list of all 676 errors (noting that several that I've seen aren't on this list), made regexes to recognize them, built a test suite, and then thought to myself, "Self, has someone done this?", followed by "Self, this is kinda lame, surely there's a better way?"
I'm happy to make a cpan module if there isn't one. Or tell me, is there a better way? I mean, dozens of daemons running on hundreds of nodes can't be simple, but this is ridiculous.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Parsing perl errors
by Fletch (Bishop) on Feb 03, 2009 at 04:37 UTC | |
by wumpus (Sexton) on Feb 05, 2009 at 21:43 UTC | |
by wumpus (Sexton) on Mar 06, 2009 at 23:14 UTC | |
by wazoox (Prior) on Mar 09, 2009 at 14:31 UTC | |
|
Re: Parsing perl errors
by jethro (Monsignor) on Feb 03, 2009 at 04:09 UTC |