RE: Re: distinguishing between failures and errors

> From: J. B. Rainsberger [mailto:jbr@xxxxxxxxxxxxxxxxxxx]
...
> > 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.)

Isn't documentation the thing that should be used to tell the
writer of code that calls yours what your code is supposed to
do, or what the caller is supposed to do (or not do)?  (At
least for code meant to be re-used, such as that implementing
an API?)





Daniel