At 01:03 PM 9/28/2001 -0500, David M. Lloyd wrote:
>On Fri, 28 Sep 2001, Alan Burlison wrote:
>
> > Arthur Bergman wrote:
> >
> > > longjmp in a controlled fashion isn't thread-safe? Or longjmping while
> > > holding mutexs and out from asynchronous handlers is not thread-safe?
> >
> > Arthur It *may* be possible to use longjmp in threaded programs in a
> > restricted fashion on some platforms. However if you use it on
> > Solaris, for example, where we don't commit to it being thread-safe
> > and it breaks - tough. This includes breakage introduced by either
> > new patches or new OS releases, as we haven't committed to it being
> > thread-safe in the first place.
>
>This raises another issue: Is the Perl_croak() thing going to stay
>around? As far as I can tell, this uses siglongjmp. I personally can't
>think of any other way to do this type of exception handling in C, so
>either we don't use croak(), find another way to do it, or just deal with
>the potential problems.
Croak's going to throw an interpreter exception. There's a little bit of
documentation about the exception handling opcodes in
docs/parrot_assembly.pod, with more to come soonish.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
