Re: Deprecated use of $SIG{__DIE_

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;
    }
}
[download]

Comment on Re: Deprecated use of $SIG{__DIE__} is useful Download Code

Replies are listed 'Best First'.
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__}`.	[reply] [d/l] [select]
Re^3: Deprecated use of $SIG{__DIE__} is useful by ikegami (Patriarch) on Feb 28, 2009 at 19:13 UTC
Indeed, thanks.	[reply]
Re^3: Deprecated use of $SIG{__DIE__} is useful by perrin (Chancellor) on Feb 28, 2009 at 23:02 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. Neither does $SIG{__DIE__}. That would be $SIG{__WARN__}.	[reply]
Re^4: Deprecated use of $SIG{__DIE__} is useful by ikegami (Patriarch) on Feb 28, 2009 at 23:07 UTC
I'm not sure what he meant by throwing undefined values, but that which strict produces is caught by `$SIG{__DIE__}`, not `$SIG{__WARN__}`.	[reply] [d/l] [select]
Re^5: Deprecated use of $SIG{__DIE__} is useful by perrin (Chancellor) on Feb 28, 2009 at 23:38 UTC


"be consistent"
	PerlMonks

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

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