Hi Bill,
Basically in Xerces, Exceptions are organized into couple of groups,
as shown below:
1. DOM_DOMException
2. SAXException
3. XMLException
4. EndOfEntityException (internal only)
From application perspective, only the first three exception need to be
taken care. You may
use 1, 3 if your application is using DOM parser, or 2, 3 for SAX parser,
and in case you worry
about missing something, you may catch the {...}.
Regards,
Peiyong Zhang
____________________________________________
XML Parsers Development
IBM Toronto Laboratory email: [EMAIL PROTECTED]
Phone: (416)448-4088; Fax: (416)448-4414; T/L: 778-4088
Bill Klein <[EMAIL PROTECTED]> on 05/02/2001 05:26:00 AM
Please respond to [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
cc:
Subject: Exception classes
Hi all,
Any reason why the classes in Xerces that can be thrown as exceptions
aren't all derived from soem common base classs? This would make life a lot
easier for programs that don't need detailed error information, and just
handle parser errors in a more general way. It would probably not be
rediculous even to derive from std::exception...
Aside from making life a bit easier, another reason I'd want this is
because I'm scared that perhaps I'm not catching all the possible types of
exceptions that Xerces can throw (or perhaps another type will be added in
the future, crashing my program, when that exception is thrown...).
But maybe I'm missing something...
-Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
