• From: David Megginson <ak117@f...>
• To: xml-dev@i...
• Date: Sun, 4 Jan 1998 13:32:27 -0500

Tim Bray writes:

 > On this one, I agree with David and disagree with James.  I don't
 > see the advantages to using an exception.  I think that a SAX processor
 > should use fatal() (why the longer fatalError()?) - this has the
 > advantage that you can, after the first message, go on looking for
 > more fatal errors.  Of course, a SAX processor must not, after the first 
 > fatal() callback, emit any more element() or charData() callbacks.

The only problem here is that the element context could be useful for
error reporting (i.e. "Error in <name> in <address> in
<frontmatter>").  When XML documents are machine generated, this type
of an error message might be more useful than a line number.


Thanks, and all the best,


David

-- 
David Megginson                 ak117@f...
Microstar Software Ltd.         dmeggins@m...
      http://home.sprynet.com/sprynet/dmeggins/

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/
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• References:
  • Re: SAX: Error Reporting (question 4 of 10)
    • From: Tim Bray <tbray@t...>

• Prev by Date: Re: SAX: External Entity Start and End (question 2 of 10)
• Next by Date: Re: SAX: Document Start and End (question 1 of 10)
• Previous by thread: Re: SAX: Error Reporting (question 4 of 10)
• Next by thread: Re: SAX: Error Reporting (question 4 of 10)
• Index(es):
  • Date
  • Thread