At 06:10 PM 1/21/01 +0000, Alan Burlison wrote:
>[EMAIL PROTECTED] wrote:
>
> > So the "gloss" is that (sig)longjmp() does not understand locks.
> > I can understand that. If all goes according to plan perl will no longer
> > longjmp() out of signal handlers. So the issue becomes other places
> > where locks can be held. With the possible exception of stdio, perl
> > is in a position to "know" about those and undo them as part of
> > its stack unwinding.
>
>Not just stdio - the whole of libc. malloc for example uses a mutex.
More than just libc--every library perl links against can potentially do
threading stuff. Though it's been my experience that little outside system
calls and the C runtime is dynamically thread safe. (If it's threadsafe at
all...)
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
