In the fast majority of the code I write, I use plain old
die, without wrapping them in
eval. But
this has more to do with the kind of programs I write than
with a deeper philosophy. Most programs I write run quickly
and are of the form "here's a bunch of things (files, arguments, environment variables, URLs), produce something".
And the something can either be produced, or it can't. So,
if there's something missing, or wrong, about the 'bunch of
things', nothing should be produced, and the program should
terminate with an error message. Which is exactly what
die does.
Programs performing database modifications do use another
technique though. There I will do things like:
eval {
start transaction or die;
...
prepare or die;
...
execute or die;
...
fetch or die;
...
};
if ($@) {
rollback;
die $@;
}
else {
commit;
}
If something goes, I die as usual, but this die will be
caught, the transaction will be rolled back, and we
cascade the die upwards (where it's most likely not caught
again).
Abigail
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.