I tend to agree. A lot of people with a lot more
experience than I have rave about how wonderful exception
handling is, but they've failed to communicate to me
why it is valuable to be able to throw an exception in
one place and catch it someplace else rather than handling
the problem (assuming it can be handled by any means other
than spitting an error message and bailing) in the same
block of code where it is detected. It seems to me that
having the exception and the handling thereof separated
by arbitrarily many lines of code is asking for headaches
in terms of code maintenance. Rather than throwing the
exception in the first place, wouldn't it be better to
handle it en situ? (Sure, sometimes a number of spots
can share the same code -- so call a subroutine then,
but at least the call is right there.)
As I said, I have a good deal less experience than
a lot of the people who rave about exception handling,
so I'm probably missing something...
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||