Re^16: Print inside SIGNALS

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.

Comment on Re^16: Print inside SIGNALS Download Code

Replies are listed 'Best First'.
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]

Replies are listed 'Best First'.

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]