Re^15: Print inside SIGNALS

And it should be obvious to anyone that I didn't hit Ctrl-C within the first two seconds

duh. I never claimed you killed it within the first two seconds. I said you killed it before <> returned, and thus before the signal handler was called.

Then you are making this same incorrect (and insulting) assumption that ikegami did.

You tried to disprove my claim that the signal handler does get called once <> returns by killing the process before it returns. So you failed. But now, you're compounding that by making stupid assumptions. Stop, and think.

Comment on Re^15: Print inside SIGNALS Select or Download Code

Replies are listed 'Best First'.
Re^16: Print inside SIGNALS by haukex (Archbishop) on Jul 20, 2018 at 19:02 UTC
Responding to your ninja edit... You tried to disprove my claim that the signal handler does get called once `<>` returns by killing the process before it returns. So you failed. But now, you're compounding that by making stupid assumptions. Stop, and think. I understand there was some ambiguity in the very first code snippet I showed, which is why I also showed further examples further down in the thread, ~~which you clearly haven't tried to run yourself on a Linux system. Until you do, and actually respond to the points I raised, I'm done with this nonsense.~~ Update: Sorry. Please see my reply here.	[reply] [d/l]
Re^17: Print inside SIGNALS by ikegami (Patriarch) on Jul 21, 2018 at 01:18 UTC
Until you do, and actually respond to the points I raised, I'm done with this nonsense. I responded to all the points you raised in replies to me. Sorry. Please see my reply here. Oh wow. That program contradicts what I said. I stand corrected. That's so weird. Perl signals can be checked explicitly by ops and XS functions if they so desire, but it's hardly done for obvious reasons. That means they specifically added a signal check in the middle of `<>`. I did not expect that!	[reply] [d/l]
Re^16: Print inside SIGNALS by haukex (Archbishop) on Jul 20, 2018 at 18:56 UTC
I said you killed it before `<>` returned, and thus before the signal handler was called. Explain the behavior of the one-liners I provided in this thread so far, ~~otherwise I have to just assume you are trolling me.~~ Update: Sorry. Please see my reply here.	[reply] [d/l]