Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
autark makes the excellent suggestion to use $SIG{__DIE__}. The die signal, AKA sigdie, can be caught and handled by a user defined function. This is done by adding the handler to the %SIG associative array. (read %SIG) I've spent plenty of time playing with this device, and I thought I might take a moment to point out a few of the pitfalls. Many of these are mentioned in the documentation for die, warn, eval, $^S, and for %SIG. (The last two are parts of perlvar.) So then, on to the pitfalls.

Pitfall 1: While eval traps the fatality of sigdie, it does not block the $SIG{__DIE__} handler from being called.

Solution 1: If you don't want your handler to be used by any eval block, then check $^S at the begining.
Solution 2: If you have a particular eval block where you don't want the handler to be invoked, then turn it off using local:
sub Something { local $@; # Don't step on other code. # try eval{ local $SIG{__DIE__}; # No sigdie handler # do stuff that might die } # catch HandleEvalError( $@ ) if $@; }

Pitfall 2: The sigdie handler can be set at any time, including during compilation (via a BEGIN block). If you set the handler during a BEGIN block and complitation fails before compiling your subroutine, you not only get a function not found error, but you lose the information about the compilation error.

Solution 1: Declare your handler subroutine before setting the handler.
  <Note>It occurs to me that you might not have realized that you can do this. Here is an example of to what I am refering. The solution is to move the subroutine up in your code, before the BEGIN block:
BEGIN{ $SIG{__DIE__} = \&FatalErr } # Real problem if compile fails before getting here. sub FatalErr { # do stuff, maybe print @_ or something. }
Why does moving the sub up work? Well... BEGIN is actually just another sub routine, except that it gets called as soon as its compiled. INIT, by the way, is also a special sub routine, except that it gets called as the last step of the compilation phase. </Note>
Solution 2: Don't set your handler in a BEGIN block like that. If you want the handle available after compilation is complete, but before code runs, then use an INIT block.

Pitfall 3: Not so much a pitfall as it is a reminder: Functions called with an ampersand and no argument list are passed the current values of @_. This means (as Plaid once pointed out to me) that your sigdie handler gets the same argument list that die got. One thing to note is that the file/line number appending has already taken place by the time your handler gets @_.

Pitfall 4: When your handler is finished, Perl continues dieing. This means that not only does the execution end, but Perl prints the error message to STDERR.

Solution: You might not have thought of that as a pitfall, but I certainly do. Sometimes you want to include a lot of information about the failure. Maybe write it to a file or something, and then make the error message the user sees be something like, "An error occurred. See log, '$log'\n". The trick here is to keep in mind that Perl is about to exit anyway, so why not accelerate the process? BTW Don't do this in your signal handler unless you are also checking $^S. People get mad when eval blocks don't return.

Pitfall 5: Your handler only gets called if you use die. This means that if you aren't checking your system calls and using die like C's Assert, then you won't get any added functionality.

Solution: die. Everywhere.

I hope this helps you out. Please do read the documentation sited above. Also, don't forget the power of an END block.

A few of my past posts on the subject:
Fun with $SIG{__DIE__}         And yet more $SIG{__DIE__} fun...         END failed--call queue aborted

In reply to SIGDIE by Adam
in thread BEGIN, END, eval and die. by zzspectrez

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, 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
  • 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.
  • Log In?

    What's my password?
    Create A New User
    [Corion]: marioroy: Heh, glad that you get enjoyment out of it! It's mainly a valve for me to vent some of the pressure ;-D
    [Corion]: Oooh - note is interesting, at least in the sense that I will steal its command line interface for my own note taking app ;-D

    How do I use this? | Other CB clients
    Other Users?
    Others contemplating the Monastery: (6)
    As of 2017-08-16 14:06 GMT
    Find Nodes?
      Voting Booth?
      Who is your favorite scientist and why?

      Results (265 votes). Check out past polls.