develooper Front page | perl.perl5.porters | Postings from January 2001

Re: Does perl really need to use sigsetjmp? (18% performancehit)

Thread Previous | Thread Next
Dan Sugalski
January 9, 2001 11:29
Re: Does perl really need to use sigsetjmp? (18% performancehit)
Message ID:
At 02:20 PM 1/9/01 +0000, Alan Burlison wrote:
>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...

Well, besides "Just don't *do* that," any thoughts on how to handle this 
properly in p6?


--------------------------------------"it's like this"-------------------
Dan Sugalski                          even samurai                         have teddy bears and even
                                      teddy bears get drunk

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About