Re: Re: distinguishing between failures and errors

> > That fact that you say using them allows the compiler
> > to 'get in the way' sounds like a non-issue.  Is this
> > coupling between your two systems?  Maybe...but I
> > (personally) would rather have it and make damn sure
> > those exceptions are handled.
> 
> If the problem is coupling, counldn't that be solved by throwing 
> java.lang.Exception?

That leads to excessive, gratuitous duplication!

> My guess is that whichever approach you choose, you still document 
> the exceptions that get thrown, right?  

Yes: it just depends who the intended audience includes. Mine does not 
include the compiler. None of its business! :)

> So the only thing you gain 
> with the suggestion above is forcing the code to be aware of the 
> Exception possibility of your code.

Yes: I submit that that is what tests are for. (If you're here, then you're 
writing tests, after all.)

--
J. B. Rainsberger,
President, Diaspar Software Services
Let's write software that people understand.
http://www.diasparsoftware.com/
telephone: +1 416 791-8603