commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Yandell <bay...@generationjava.com>
Subject Re: [lang][collections] Utils having a public constructor
Date Tue, 13 Aug 2002 20:20:59 GMT
I'm of the same opinion. So +1. I suspect we may be the only ones in this
camp though :)

I guess I should send this out as a new thread with [VOTE] on it and try
to get some resolution. Will do in a bit.

Hen

On Tue, 13 Aug 2002 costinm@covalent.net wrote:

> I would vote for public. Sort of 'be liberal in what you accept'.
> If it helps velocity - it may also help others, and it doesn't hurt others
> too much.
>
> In the cases where a singleton is actually required we should of
> course use private constructor - but this is not the case in any of the
> utils I've seen. So if singleton is not required, why enforce it,
> especially when some projects are affected ?
>
>
> Costin


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


Mime
View raw message