[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: SAX: Exception Handling
> > throws java.lang.Exception > > { > > [..] > > } > > > > The Java compiler will not help me discover which constructors or > > methods invoked in the body can throw exceptions that I have not yet > > considered. > > Right, so don't do that. Declaring an *interface* as throws > java.lang.Exception does not constrain an *implementation* of that > interface to be declared as throws java.lang.Exception. It can be > declared to throw the appropriate subclass of java.lang.Exception. But then since application programmers write to interfaces, not implementations, then application programmers would have all those nasty problems with getting handed random exceptions. A primary intent of exception declarations is to constrain the kinds of errors that a substystem (e.g. parser) reports, so that its clients have a clean "contract" and know exactly the kinds of "expected faults" they have to deal with. Clauses like "throws Exception" are basically counter to the core philosophy of exceptions in Java. - Dave 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...)
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|