in reply to trap signal 'exit': why I am not able to have it work??

I have trouble reading your post, please don't use <pre> tags for normal text.

update

From my understanding are handlers %SIG supposed to process external (OS specific) signals send from a kill command to the process, maybe with the only exception of warn and die which are not signals but internal hooks.

see also perlipc#Signals

I couldn't find any mention of the possibility to intercept exit() with a sighandler

But this "trapping exit() calls with %SIG" explicitly shows how to execute code in an END block after exit .

Cheers Rolf
(addicted to the Perl Programming Language and ☆☆☆☆ :)
Je suis Charlie!

Replies are listed 'Best First'.
Re^2: trap signal 'exit': why I am not able to have it work?? (updated)
by alex5161 (Novice) on Oct 31, 2017 at 13:11 UTC

    Sorry for uncomfortability of < pre >, but on < p > I do not like big intervls; without anything - I hate spagety lines...

    Yes, the END{} completely fine with me.

    Thanks!

      > Sorry for uncomfortability of < pre >, but on < p > I do not like big intervls; without anything - I hate spagety lines...

      And the monastery hates <pre> tags and you are free to use <br> tags ... :)

      please see Markup in the Monastery

      Tags You Should NOT Use

      At first blush, the <pre> ...</pre> pair may look like an alternative to code tags... BUT DON'T USE IT HERE chiefly because <pre>...</pre> tags will not persuade the Monastery to provide a download link for the contents of the <pre> ... and while it is now supposed to wrap lines that are too long for the viewer's browser window, there are ways Monks could use CSS that would defeat that. So, please. don't use <pre>...</pre> .

      If you want I wrote a "wiki" add on for the monastery in JS facilitating the creation of posts (especially on mobiles)

      Cheers Rolf
      (addicted to the Perl Programming Language and ☆☆☆☆ :)
      Je suis Charlie!

        Ahha!  <br> !!
        Perfect! Will use it!
        Thanks!