• From: "Mark D. Anderson" <mda@d...>
• To: XMLDev list <xml-dev@i...>
• Date: Tue, 21 Dec 1999 13:02:19 -0800

> 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?

there are also potential MT issues which i mentioned on a SAX2 thread
a few weeks ago.

-mda


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo@i... the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Follow-Ups:
  • Re: SAX2: Exceptions
    • From: David Megginson <david@m...>
  • Re: SAX2: Exceptions
    • From: David Brownell <david-b@p...>

• References:
  • SAX2: Exceptions
    • From: David Megginson <david@m...>

• Prev by Date: Re: The per-element-type namespace partition
• Next by Date: RE: Appending a Doctype node using Microsoft's XML COM interfaces
• Previous by thread: Re: SAX2: Exceptions
• Next by thread: Re: SAX2: Exceptions
• Index(es):
  • Date
  • Thread