Do NOT, however, use $SIG::{__DIE__} in anything you intend to distribute through CPAN.

More than once I have wasted an hour or two tracking a bug that was having its error messages swallowed by a CPAN module that blithely used an unlocalized $SIG::{__DIE__} handler for its own error processing and did not propagate unknown errors. Thereby stomping all over my application's own error handling (and any other module that might need to 'die').

It only takes one mis-use of $SIG::{__DIE__} anywhere in a body of code to mess it up for everyone. It is much too fragile for use in general release code.

In reply to Re^2: Opinions of Error.pm by snowhare
in thread Opinions of Error.pm by harryf

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.