> There is so much brokenness and platform-dependent behaviour in the area > of perl signal handling that I don't think a switch from sigsetjmp to > setjmp is going to make any discernable difference. That's the best reason I've seen so far :-). It also occurs to me that one of the safe signal proposals floating around was to make the C-level signal handler just set a flag and have the Perl-level handler called later. If that ever happened there would certainly be no reason to use sigsetjmp because no perl code would ever actually run across a signal handler border.Thread Previous | Thread Next