[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. > >> The short answer is *never use them* in a multithreaded application. > > But the short answer (while it may suffice for perl6) is no use to me > as a perl5 maintainer. Well, we all have our particular crosses to bear ;-) At the risk of being boring: Threads in perl5 are irredeemably broken and should not be used. Alan Burlison
