comment on

Personally, I suggest you don't use $SIG{__DIE__} and instead use eval. I find the whole design of $SIG{__DIE__} to be flawed. It can be useful in limited circumstances but it can't scale well and I find it best to just avoid it.

But, if you do use $SIG{__DIE__}, then you need to know about $^S: "True if inside an eval(), otherwise false." so you can do:

    $SIG{__DIE__}= sub {
        die @_   if  $^S;
        # rest of code here
    };
[download]

for example.

Update: How do you replace $SIG{__DIE__} with eval, you ask?

    $SIG{__DIE__}= sub {
        die @_   if  @^S;
        doStuffWith( $_[0] );
    };
    doEverythingElse();
    exit 0;
[download]

becomes

    eval {
        doEverythingElse();
        1;
    } or do {
        doStuffWith( $@ );
    };
    exit 0;
[download]

or thereabouts.

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

In reply to (tye)Re: die hooks, signal handlers and eval, all mixed up by tye
in thread die hooks, signal handlers and eval, all mixed up by Amoe

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


We don't bite newbies here... much
	PerlMonks