[Expat-discuss] Exiting expat handlers

[Karl Waclawek]

> I was relying on a section that Sun puts at the end of each man page. It
> rates the thread compatibility of each function. Sometimes they explain
> the reasons, sometimes they don't. In the case of setjmp/longjmp they
> are rated "Unsafe", which is the worst thread compatibility rating they
> have. Since different threads have different stacks it would seem
> possible to manage a multi-thread version of jumps. I suspect these
> functions were just implemented on Solaris with some global variables
> and never updated to a thread specific form.

I am sorry to read that. ;-(

We are planning to add return values to the Expat handlers, such that
an application error will be passed back to Expat and the parser
will then return immediately. 

Hopefully we will some time for implementation around the end of the year.
But this will be part of Expat 3.0 - right now we are trying to
finish off Expat 2.0. The current CVS is already quite close, I believe.

Karl