On 4-Dec-07, at 9:03 AM, Stian Soiland wrote:
On 12/3/07, Paul J. Lucas <[EMAIL PROTECTED]> wrote:
Funny, because java.io.FileNotFoundException is derived from
IOException. So clearly there's precedent.
Did you notice the "io" package name? :-) The exceptions here are
about resources, not IO.
Thinking again, can both positions can be satisfied with, somewhere
under IOException, a base class for exceptions with 'resource'
semantics (not found, forbidden) and another for those with transport/
failure semantics?
Forgive me if I'm stating the obvious :)
--Toby
Generally I think having support for throwing exceptions for setting
result status codes and exiting at the same time is a very good thing,
...
