Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw
 
PerlMonks  

Re: Deprecated use of $SIG{__DIE__} is useful

by ikegami (Pope)
on Feb 28, 2009 at 19:03 UTC ( #747188=note: print w/ replies, xml ) Need Help??


in reply to Deprecated use of $SIG{__DIE__} is useful

I'm not sure of the reason for the deprecation, but how is that different from the recommended

BEGIN { *CORE::GLOBAL::die = sub { CORE::die @_ if ref $_[0] || ! defined $^S; my ($class) = caller(0); @_ = ( $class, 'Uncaught', join( '', @_ ) ); goto $class->can('throw') || \&throw; } }


Comment on Re: Deprecated use of $SIG{__DIE__} is useful
Download Code
Re^2: Deprecated use of $SIG{__DIE__} is useful
by clinton (Priest) on Feb 28, 2009 at 19:09 UTC

    Overriding die catches calls to die('Error'), but it doesn't catch errors such as undefined values being thrown because I've used strict.

    In situations like this, where your code behaves in an unexpected way, it is useful to have a stack trace to see how we got to that point in the code, which I can only do with $SIG{__DIE__}.

      Indeed, thanks.

      Overriding die catches calls to die('Error'), but it doesn't catch errors such as undefined values being thrown because I've used strict.

      Neither does $SIG{__DIE__}. That would be $SIG{__WARN__}.

        I'm not sure what he meant by throwing undefined values, but that which strict produces is caught by $SIG{__DIE__}, not $SIG{__WARN__}.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://747188]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others studying the Monastery: (13)
As of 2014-07-10 15:24 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    When choosing user names for websites, I prefer to use:








    Results (213 votes), past polls