[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: SAX2: Should SAXException extend IOException?
On Mon, 3 Jan 2000, David Brownell wrote: > "Clark C. Evans" wrote: > > I guess I'm trying to say that a data format > > exception in one context could easily be seen > > as an I/O exception in another context. > > Actually, everything boils down to an EINVAL at > some level ... everything else is just varying > layers of sugar to explain what was INVAL ! ;-) Yes. And the detail of such sugar should depend upon the task being performed. A SAX parser is not a library of functions each performing distinct granular and possibly recoverable operations. Rather, a SAX parser is a processing component which takes an XML input source and generates an event stream as output. It's internal workings are encapsulated -- it does not expose highly granular control of its process. Thus, possible automated recover schemes are (understandably) rather limited. Therefore, it seems perfectly acceptable for the error to be generic. Further, if you consider the SAX parser's primary task, that of converting an input source to an output stream, of the generic errors, IOException seems the best fit. Clark 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 unsubscribe, mailto:majordomo@i... the following message; unsubscribe 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
|