One approach I've been using is to define a &fail
sub, and use it in place of die() throughout my code. I.e.
open (FILE, ">>$file") or fail "Couldn't open $file";
fail then decides how to act, given the string.
It can simply log and die, or it can parse the string and
warn instead of dying.
This gets slightly messy with multiple modules, but that's eased if you're using OO, so long as fail sits up top in your objects' family tree and you're using $self->fail.
The really tricky thing about this approach is that if you want die/warn to correctly report the line number, you're going to have to play with caller.
But for real power, look into Error.pm, which could be described as an OO eval on steroids.
-- Frag.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.