in reply to Re^14: Print inside SIGNALS
in thread Print inside SIGNALS

In this part:

(1. ctrl-c pressed < 2 seconds 2. ctrl-c pressed > 2 seconds)

It was me who pressed ctrl-c within 2 seconds to show the output of the program when I would. I have never said that you did.

So fine, I feel that you that you are twisting my words and I guess this is the way you want to go, so let this be the last time I will bring up an issue with you. I've never tried to insult you. I guess that's what you get speaking out to 'popular' monks. Disregards of whatever I tried to bring up.

Replies are listed 'Best First'.
Re^16: Print inside SIGNALS
by haukex (Archbishop) on Jul 19, 2018 at 22:51 UTC

    You are right that my post is a bit harsh. I let my annoyance with this whole sub-thread affect my reply to you too much, and I apologize.

    I have re-read your posts (I just haven't had a chance to try out your code in the "edit 2" because it's getting late). If I understand correctly, the main point you were making is that an unhandled SIGINT means that Perl doesn't get to flush its buffers, while a clean exit does. You are of course right in that, as well as in your point that STDERR is unbuffered by default. If I'm missing anything else, please feel free to point it out.

    I would ask this of you though: Assume for a moment that going into this discussion, I already knew the behavior of SIGINT, STDOUT, and STDERR. If you keep that in mind when looking over the thread, perhaps you can see my point of view of how this thread went, and maybe also why I disagreed with you (in the context of this thread) that "both of you are correct".

      If I understand correctly, the main point you were making is that an unhandled SIGINT means that Perl doesn't get to flush its buffers

      For the fifth time, no. That's what *you* keep saying, and it's wrong.

      Because you pressed Ctrl-C, the signal handler didn't get called at all. There never was a print, so there wasn't anything to flush.