• From: David Megginson <david@m...>
• To: "XML Developers' List" <xml-dev@i...>
• Date: Mon, 8 Mar 1999 06:41:38 -0500 (EST)

James Clark writes:

 > Wouldn't it be simpler to throw different type of exception in these two
 > cases?  You could have a SAXNotRecognizedException that extends
 > SAXNotSupportedException, and say that parsers should throw
 > SAXNotRecognizedException when the reason they don't support a feature
 > is that they do not recognize the feature.

Yes, I agree.


All the best,


David

-- 
David Megginson                 david@m...
           http://www.megginson.com/

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 (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:
  • SAX RFD: ModSAX Predefined Features
    • From: David Megginson <david@m...>
  • Re: SAX RFD: ModSAX Predefined Features
    • From: James Clark <jjc@j...>

• Prev by Date: Re: SAX RFD: ModSAX Predefined Features
• Next by Date: SAX: ModSAX addition, general property query
• Previous by thread: Re: SAX RFD: ModSAX Predefined Features
• Next by thread: XSL Problem
• Index(es):
  • Date
  • Thread