• From: Jarle Stabell <jarle.stabell@d...>
• To: "'xml-dev@i...'" <xml-dev@i...>
• Date: Tue, 16 Feb 1999 00:26:23 +0100

David Megginson wrote:

>   public interface ModParser extends Parser
>   {
>     public abstract void setFeature (String featureID, boolean state)
>       throws SAXNotSupportedException;
>
>     public abstract void setHandler (String handlerID, ModHandler 
handler)
>       throws SAXNotSupportedException;
>   }

Is it obvious that one should throw exceptions on not supported?
I believe it in many cases would be more comfortable if it returned a 
boolean supported or not instead of throwing an exception, as many clients 
probably want/need to check whether a particular feature is supported or 
not (and trade off behaviour accordingly)


Cheers,
Jarle


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...)

• Follow-Ups:
  • RE: ModSAX (SAX 1.1) Proposal
    • From: David Megginson <david@m...>

• Prev by Date: ModSAX (SAX 1.1) Proposal
• Next by Date: X3D
• Previous by thread: X3D
• Next by thread: RE: ModSAX (SAX 1.1) Proposal
• Index(es):
  • Date
  • Thread