Nicholas Clark wrote: > and as you can install any perl subroutine as a signal handler, I'd infer > that any part of perl might actually be running in a signal handler. > [and might die back out to an eval that started before %SIG{} was touched, > so I don't even think the idea of switching to sigsetjump() when the first > %SIG{} assignment is made would work] > > I don't think it's possible to win. No, I think you are right. However the whole signal/eval/die/setjmp/longjmp mess is pretty much broken anyway, what with the non-MT safeness and the current bizzare behaviour illustrated by Raphaels test script. I'm still intending to disable sigsetjmp - I havn't heard any decent reason for it being used. Roll on perl6... Alan BurlisonThread Previous | Thread Next