commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Colebourne <>
Subject Re: [all][math] Help wanted with exceptions API design
Date Wed, 02 Feb 2011 08:57:10 GMT
On 2 February 2011 00:12, Gilles Sadowski <> wrote:
>> Here is a probably too simple example:
>> com.example defines IOException
>> com.example.input uses IOException
>> com.example.output uses IOException
> Well, I don't see that as obviously better than storing all exceptions in an
> "exception" package. I find the latter tidier.
> The problems arises when one thinks that some exception is only needed in
> one package:
> uses and defines FooException
> Then one discovers
> also uses FooException
> Add a few more exceptions and soon people are searching the exceptions
> definitions all over the place, or create new ones that duplicate
> functionality that already exists in some other package.

I too would consider an exceptions package bad practice. Exceptions
should be located in the highest level package that they might be used
from. "tidiness" is generally a bad metric for organising package


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message