commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Yandell <>
Subject Re: [IO] IOUtils, etc...
Date Mon, 16 Aug 2004 18:31:14 GMT

Old reason.

There are tools (like Velocity) for which the public constructors are a
lot of help, so after a lot of discussion we've ended on a pattern of
allowing public constructors but slapping big warnings on the javadoc.

If someone mistakenly uses the public constructor to do things, it's not
really going to hurt them too much so the velocity guys win out.


On Mon, 16 Aug 2004 wrote:

> Utility classes like IOUtils only contain static methods and are not meant
> to be instantiated; so, why not make their constructors private?  That
> would enforce non-instantiation instead of just suggesting it in the
> JavaDoc.
> Thanks,
>    Jamie
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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

View raw message