Talk:c/program/signal

exceptions to undefined behavior
I struggle with the double negative. Should "not" be deleted from "signal with the first argument not being the number of the signal currently handled."? 7.14.1.1/5 ("the signal function with the first argument equal to the signal number corresponding to the signal that caused the invocation of the handler.") seems to imply that a signal handler may re-register itself. Newatthis (talk) 05:16, 27 June 2015 (PDT)
 * right. (btw, the example on raise was fine as it was) --Cubbi (talk) 09:33, 27 June 2015 (PDT)
 * OK, I reinstalled the earlier example on raise. I thought that I saw a conflict with typical usage and undefined behavior. Newatthis (talk) 04:44, 28 June 2015 (PDT)