I wondering if anyone has adopted a consistent approach to handling ( and generating ) exceptions in perl, including supplying explanatory text about the exception or failure.

I've seen:

  1. subs that return 0 or undef on failure
  2. subs that die(), expecting the caller to wrap them in an eval block to catch failures, and use $@ to get the error text.
  3. subs that know the errors are OS related and thus set $! or $^E.
  4. subs that put error explanations into globals
  5. subs that call warn(), and expect the caller to muck with $SIG{__WARN__} to get context about the error
  6. use Carp;
  7. etc, etc
I've read perldoc perlvar, and the "Error Indicators" section, as well as the Carp docs, and $SIG{__WARN|DIE__} areas of perlipc.

Does anyone have any thoughts on how I should approach passing error conditions and return values around in my own code ?

In reply to Exceptions and Return Codes by kschwab

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.