commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Colebourne" <scolebou...@btopenworld.com>
Subject Re: [collections] XxxUtils inner classes
Date Wed, 02 Apr 2003 20:21:04 GMT
In an ideal world (ie. a fresh start for [collections]) I would create
subpackages. I guess I'm a natural grouper, and find javas lack of a
subpackage scope very annoying.

Its too late for [collections], and one package must remain.

I remain unconvinced about the need to break out the inner classes though. I
do judge the complexity of an API by the number of visible classes in the
javadoc/ real java files. Even as package private I would find these many
classes distinctly annoying, and they would get in the way of me
understanding the API. I'm -0.5 at present on breaking out the inner
classes.

Stephen

----- Original Message -----
From: "Alex Chaffee / Purple Technology" <guru@stinky.com>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Sent: Wednesday, April 02, 2003 9:03 PM
Subject: Re: [collections] XxxUtils inner classes


> On Wed, Apr 02, 2003 at 11:13:00AM -0700, David Graham wrote:
> > I see no problem with using just 1 package
org.apache.commons.collections.
> > Sub-packages are not needed and violate the "package is the unit of
release"
> > principle.
>
> Yes.  Subpackaging bad.  import org.apache.commons.collections.* good.
>
>  - A
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message