in reply to Re: Checking the success of eval
in thread Checking the success of eval

I consider eval to be an essential feature of Perl and $SIG{__DIE__} to be a mostly bad idea. So if you want to fix the buggy conflict that they have, I really think you should be fixing the die handler and not the eval: 

$SIG{__DIE__}= sub {
    return   if  $^S;
    print "Caught by die handler: @_";
    exit;
}

[download]

Better still is to avoid die handlers altogether and either use eval to catch the exception or use a destructor or END block to do the clean up.

        - tye (but my friends call me "Tye")

Replies are listed 'Best First'.
Re: (tye)Re: Checking the success of eval
by ncw (Friar) on Apr 21, 2001 at 02:31 UTC
    Thank you for that $^S nugget tye - I shall faithfully inscribe this into all my $SIG{__DIE__} handlers :-)

    I agree with you that eval is essential, but I disagree with you that $SIG{__DIE__} is a completely bad idea. Just think of if like an eval { } or do_stuff round your entire code and you could come to love it ;-) (If it actually worked that way of course!)

    I like $SIG{__DIE__} for CGI's in the form of CGI::Carp which is really very useful - it would be tiresome to be doing that with eval. I also like $SIG{__DIE__} so I can write scripts which mail me when they've blown up!

    I don't see how you would do it with an END block - perhaps you could enlighten me there? How do you know in an END block whether your program is dieing or just exiting and if you can tell how do you get the value of $@ (presuming that some other destructor/END block used eval)?

[reply]

In Section Meditations