commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Colebourne" <>
Subject Re: [collections] Utility class names [was Collections Next Gen]
Date Wed, 02 Apr 2003 20:29:43 GMT
Actually the mistake was made by me not pushing hard enough for better named
static utility classes. My original proposal was:



The advantage with this scheme is now obvious in that it would have
emphasised the functionality, rather than the collections type. (It also
ties together similar functionality in the implementations) We could make
this change now, but it would cause major deprecations.


From: "Henri Yandell" <>
> I think the documentation for Collections should talk in terms of features
> and not classes. ie) Commons-Collections provides the following features:
>               Map                Set          List
> ordered        y                  n            -
> sequenced      y                  n            -
> unique         y                  -            n
> etc. Accessing said feature would be through the MapUtils class at all
> times. Then people can quite easily learn the API by just using the
> feature matrix to work out just what is possible.
> There would be a separate piece of documentation which would discuss
> replacements for HashMap, LinkedList etc, but I believe these are the
> exceptions and not the common case.
> Hen
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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

View raw message