According to the man page, your code would propagate the die -- but only if executing an eval. Why not always do it?

Not quite. I propagated the die without further action if executing an eval.

I left up to you what to do when outside of any eval, likely something followed by die or exit.

I don't really see the difference between using $SIG{__DIE__} and overriding CORE::GLOBAL::die, so you might as well use the latter. 

BEGIN {
   *CORE::GLOBAL::die = sub {
      CORE::die(@_) if $^S;
      ...
   };
}

BEGIN {
   *CORE::GLOBAL::warn = sub {
      ...
   };
}

[download]

We still need to check $^S, so I don't understand the warning perlvar gives.

Anyway, in light of the warning in perlvar, what "difficult to track down" errors am I apt to run into, here?

I don't know.

In reply to Re^3: logging, to include unhandled exceptions by ikegami
in thread logging, to include unhandled exceptions by klassa

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.