• To: Paul R Brown <prb@f...>, XML Developers List <xml-dev@l...>
• Subject: Re: Seeking SAXException pattern
• From: Elliotte Harold <elharo@m...>
• Date: Mon, 29 Nov 2004 04:51:58 -0500
• In-reply-to: <A4B93D07-4196-11D9-A4EA-000A95930770@f...>
• References: <D369065E-40D3-11D9-BB2B-000A95A51C9E@t...> <41A9B0D3.4030102@f...> <41A9DEAA.3060909@m...> <A4B93D07-4196-11D9-A4EA-000A95930770@f...>
• User-agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20040910

Paul R Brown wrote:


> Interesting.  Isn't RuntimeException intended to report an error in the 
> application as opposed to an error in the input?  This has always been 
> my opinion and practice.


Yes, that's normally how it works, and how it should work. But if you 
really don't like wrapping your checked exceptions, it is another 
option. Languages like C++ that only have runtime exceptions don't have 
to deal with this problem in callback APIs.

-- 
Elliotte Rusty Harold  elharo@m...
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim

• References:
  • Seeking SAXException pattern
    • From: Tim Bray <tbray@t...>
  • Re: Seeking SAXException pattern
    • From: Mik Lernout <mik@f...>
  • Re: Seeking SAXException pattern
    • From: Elliotte Harold <elharo@m...>

• Prev by Date: Re: Relax NG, Thoughts, etc.
• Next by Date: RE: Relax NG, Thoughts, etc.
• Previous by thread: Re: Seeking SAXException pattern
• Next by thread: RE: Seeking SAXException pattern
• Index(es):
  • Date
  • Thread