david-b at pacbell.net
Tue Dec 21 21:28:21 GMT 1999
"Mark D. Anderson" wrote:
> > 5. Have all callbacks that formerly threw SAXException throw
> > IOException instead. This should help to avoid a lot of exception
> > tunneling.
> when you say "throw", do you mean a native C++ raising of an exception?
> or you mean an error handler?
> will there be both?
> which ones are continuable?
Neither Java nor C++ has "continuable" exceptions; what are you
> there are also potential MT issues which i mentioned on a SAX2 thread
> a few weeks ago.
Perhaps you could give a pointer to the archive entry.
There should be no MT issues, beyond the fact that multithreaded C++
isn't standardized. Any "catch" clauses clearly need to operate in
exactly the context of the thread whose stack is being unwound, and
be able to release locks owned by that thread.
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo at ic.ac.uk the following message;
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)
More information about the Xml-dev