Lists Home |
Date Index |
- From: Norbert Mikula <email@example.com>
- To: firstname.lastname@example.org
- Date: Wed, 4 Jun 1997 17:02:04 +0200 (MET DST)
NXP, as of today, simply prints error messages to Stderr.
This is fine for now, but it is certainly not the best
way to do things.
There was a suggestion made to me, to throw
an exception, but I think exceptions are not
the best solution as recovery from them is practically
not possible (From the level of the application
To my understanding there are several classes
of errors that can be passed along
2.) WF violations
3.) Violations with respect to the DTD
4.) In general these errors that are reportable - if the user wishes
Should they be handled differently ?
I was thinking in terms of "callback" functions. Like
I do it right now with the "Esis" interface.
How would you, as the user/developer community envision
What information would you like to have passed along
to an application ? Error code, textual description (what
about localization ..).
Norbert H. Mikula
= SGML, XML, DSSSL, Intra- & Internet, AI, Java
xml-dev: A list for W3C XML Developers
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To unsubscribe, send to email@example.com the following message;
List coordinator, Henry Rzepa (firstname.lastname@example.org)