You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Stephen Colebourne <sc...@btopenworld.com> on 2003/12/03 15:28:14 UTC
[collections] pairs package name
The pairs package name is perhaps not quite right. I would like the package
to hold all non-collection data structure:
- MapEntry
- KeyValue
- MultiKey
How about renaming the package to data?
(no backwards compatability issues)
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [collections] pairs package name
Posted by Stephen Colebourne <sc...@btopenworld.com>.
The package exists because we have the KeyValue interface that represents a
KeyValue without the MapEntry equals/hashcode semantics. If it were decided
that this is an inappropriate class for collections, then the package would
disappear (map entries put in maps package - multikey in main package or map
package).
Stephen
----- Original Message -----
From: "Rodney Waldhoff" <rw...@apache.org>
> Maybe I just need to dig into this more deeply, but I find any form of
> Pair or Object[2] class being exposed as a public interface of
> commons-collections a bit questionable.
>
> On Wed, 3 Dec 2003, __matthewHawthorne wrote:
>
> > o.a.c.c.data could work.
> >
> > some other ideas:
> > o.a.c.c.types
> > o.a.c.c.elements
> >
> > Stephen Colebourne wrote:
> > > KeyValue is not directly associated with maps - its a free form key
value
> > > pair. MultiKey could also be used in a List or Set.
> > >
> > > Stephen
> > >
> > > ----- Original Message -----
> > > From: "Rodney Waldhoff" <rw...@apache.org>
> > >
> > >>Why can't these all just go with the maps?
> > >>
> > >>On Wed, 3 Dec 2003, Stephen Colebourne wrote:
> > >>
> > >>
> > >>>The pairs package name is perhaps not quite right. I would like the
> > >
> > > package
> > >
> > >>>to hold all non-collection data structure:
> > >>> - MapEntry
> > >>> - KeyValue
> > >>> - MultiKey
> > >>>
> > >>>How about renaming the package to data?
> > >>>(no backwards compatability issues)
> > >>>
> > >>>Stephen
> > >>>
> > >>>
> > >>>---------------------------------------------------------------------
> > >>>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > >>>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> > >>>
> > >>>
> > >>
> > >>--
> > >>- Rod <http://radio.weblogs.com/0122027/>
> > >>
> > >>---------------------------------------------------------------------
> > >>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
> >
> >
>
> --
> - Rod <http://radio.weblogs.com/0122027/>
>
> ---------------------------------------------------------------------
> 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
Re: [collections] pairs package name
Posted by Phil Steitz <ph...@steitz.com>.
Stephen Colebourne wrote:
> I'll suggest keyvalue to positively describe the package (rather than
> negatively). That name allows MapEntry, KeyValue and MultiKey.
>
> (data/holders/elements all seem a bit vague)
>
> Stephen
>
+1
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [collections] pairs package name
Posted by Stephen Colebourne <sc...@btopenworld.com>.
I'll suggest keyvalue to positively describe the package (rather than
negatively). That name allows MapEntry, KeyValue and MultiKey.
(data/holders/elements all seem a bit vague)
Stephen
From: "Phil Steitz" <ph...@steitz.com>
> Rodney Waldhoff wrote:
> > Maybe I just need to dig into this more deeply, but I find any form of
> > Pair or Object[2] class being exposed as a public interface of
> > commons-collections a bit questionable.
>
> I agree with you, but I don't think that anything like that exists
> currently. I also agree with your comment below that all current
> contents could go into the map package. If we want to keep these things
> separate, I would prefer either the current name or "elements". I do
> not like the concept of "all non-collection data structures" since I
> don't like packages defined by exclusion.
>
> >
> > On Wed, 3 Dec 2003, __matthewHawthorne wrote:
> >
> >
> >>o.a.c.c.data could work.
> >>
> >>some other ideas:
> >>o.a.c.c.types
> >>o.a.c.c.elements
> >>
> >>Stephen Colebourne wrote:
> >>
> >>>KeyValue is not directly associated with maps - its a free form key
value
> >>>pair. MultiKey could also be used in a List or Set.
> >>>
> >>>Stephen
> >>>
> >>>----- Original Message -----
> >>>From: "Rodney Waldhoff" <rw...@apache.org>
> >>>
> >>>>Why can't these all just go with the maps?
> >>>>
> >>>>On Wed, 3 Dec 2003, Stephen Colebourne wrote:
> >>>>
> >>>>
> >>>>
> >>>>>The pairs package name is perhaps not quite right. I would like the
> >>>>
> >>>package
> >>>
> >>>
> >>>>>to hold all non-collection data structure:
> >>>>>- MapEntry
> >>>>>- KeyValue
> >>>>>- MultiKey
> >>>>>
> >>>>>How about renaming the package to data?
> >>>>>(no backwards compatability issues)
> >>>>>
> >>>>>Stephen
> >>>>>
> >>>>>
> >>>>>---------------------------------------------------------------------
> >>>>>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> >>>>>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >>>>>
> >>>>>
> >>>>
> >>>>--
> >>>>- Rod <http://radio.weblogs.com/0122027/>
> >>>>
> >>>>---------------------------------------------------------------------
> >>>>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
> >>
> >>
> >
> >
>
>
>
>
> ---------------------------------------------------------------------
> 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
Re: [collections] pairs package name
Posted by Phil Steitz <ph...@steitz.com>.
Rodney Waldhoff wrote:
> Maybe I just need to dig into this more deeply, but I find any form of
> Pair or Object[2] class being exposed as a public interface of
> commons-collections a bit questionable.
I agree with you, but I don't think that anything like that exists
currently. I also agree with your comment below that all current
contents could go into the map package. If we want to keep these things
separate, I would prefer either the current name or "elements". I do
not like the concept of "all non-collection data structures" since I
don't like packages defined by exclusion.
>
> On Wed, 3 Dec 2003, __matthewHawthorne wrote:
>
>
>>o.a.c.c.data could work.
>>
>>some other ideas:
>>o.a.c.c.types
>>o.a.c.c.elements
>>
>>Stephen Colebourne wrote:
>>
>>>KeyValue is not directly associated with maps - its a free form key value
>>>pair. MultiKey could also be used in a List or Set.
>>>
>>>Stephen
>>>
>>>----- Original Message -----
>>>From: "Rodney Waldhoff" <rw...@apache.org>
>>>
>>>>Why can't these all just go with the maps?
>>>>
>>>>On Wed, 3 Dec 2003, Stephen Colebourne wrote:
>>>>
>>>>
>>>>
>>>>>The pairs package name is perhaps not quite right. I would like the
>>>>
>>>package
>>>
>>>
>>>>>to hold all non-collection data structure:
>>>>>- MapEntry
>>>>>- KeyValue
>>>>>- MultiKey
>>>>>
>>>>>How about renaming the package to data?
>>>>>(no backwards compatability issues)
>>>>>
>>>>>Stephen
>>>>>
>>>>>
>>>>>---------------------------------------------------------------------
>>>>>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>>>>>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>>>>
>>>>>
>>>>
>>>>--
>>>>- Rod <http://radio.weblogs.com/0122027/>
>>>>
>>>>---------------------------------------------------------------------
>>>>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
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [collections] pairs package name
Posted by Rodney Waldhoff <rw...@apache.org>.
Maybe I just need to dig into this more deeply, but I find any form of
Pair or Object[2] class being exposed as a public interface of
commons-collections a bit questionable.
On Wed, 3 Dec 2003, __matthewHawthorne wrote:
> o.a.c.c.data could work.
>
> some other ideas:
> o.a.c.c.types
> o.a.c.c.elements
>
> Stephen Colebourne wrote:
> > KeyValue is not directly associated with maps - its a free form key value
> > pair. MultiKey could also be used in a List or Set.
> >
> > Stephen
> >
> > ----- Original Message -----
> > From: "Rodney Waldhoff" <rw...@apache.org>
> >
> >>Why can't these all just go with the maps?
> >>
> >>On Wed, 3 Dec 2003, Stephen Colebourne wrote:
> >>
> >>
> >>>The pairs package name is perhaps not quite right. I would like the
> >
> > package
> >
> >>>to hold all non-collection data structure:
> >>> - MapEntry
> >>> - KeyValue
> >>> - MultiKey
> >>>
> >>>How about renaming the package to data?
> >>>(no backwards compatability issues)
> >>>
> >>>Stephen
> >>>
> >>>
> >>>---------------------------------------------------------------------
> >>>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> >>>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >>>
> >>>
> >>
> >>--
> >>- Rod <http://radio.weblogs.com/0122027/>
> >>
> >>---------------------------------------------------------------------
> >>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
>
>
--
- Rod <http://radio.weblogs.com/0122027/>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [collections] pairs package name
Posted by __matthewHawthorne <ma...@phreaker.net>.
o.a.c.c.data could work.
some other ideas:
o.a.c.c.types
o.a.c.c.elements
Stephen Colebourne wrote:
> KeyValue is not directly associated with maps - its a free form key value
> pair. MultiKey could also be used in a List or Set.
>
> Stephen
>
> ----- Original Message -----
> From: "Rodney Waldhoff" <rw...@apache.org>
>
>>Why can't these all just go with the maps?
>>
>>On Wed, 3 Dec 2003, Stephen Colebourne wrote:
>>
>>
>>>The pairs package name is perhaps not quite right. I would like the
>
> package
>
>>>to hold all non-collection data structure:
>>> - MapEntry
>>> - KeyValue
>>> - MultiKey
>>>
>>>How about renaming the package to data?
>>>(no backwards compatability issues)
>>>
>>>Stephen
>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>>>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>>
>>>
>>
>>--
>>- Rod <http://radio.weblogs.com/0122027/>
>>
>>---------------------------------------------------------------------
>>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
Re: [collections] pairs package name
Posted by Stephen Colebourne <sc...@btopenworld.com>.
KeyValue is not directly associated with maps - its a free form key value
pair. MultiKey could also be used in a List or Set.
Stephen
----- Original Message -----
From: "Rodney Waldhoff" <rw...@apache.org>
> Why can't these all just go with the maps?
>
> On Wed, 3 Dec 2003, Stephen Colebourne wrote:
>
> > The pairs package name is perhaps not quite right. I would like the
package
> > to hold all non-collection data structure:
> > - MapEntry
> > - KeyValue
> > - MultiKey
> >
> > How about renaming the package to data?
> > (no backwards compatability issues)
> >
> > Stephen
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> >
>
> --
> - Rod <http://radio.weblogs.com/0122027/>
>
> ---------------------------------------------------------------------
> 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
Re: [collections] pairs package name
Posted by Rodney Waldhoff <rw...@apache.org>.
Why can't these all just go with the maps?
On Wed, 3 Dec 2003, Stephen Colebourne wrote:
> The pairs package name is perhaps not quite right. I would like the package
> to hold all non-collection data structure:
> - MapEntry
> - KeyValue
> - MultiKey
>
> How about renaming the package to data?
> (no backwards compatability issues)
>
> Stephen
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
--
- Rod <http://radio.weblogs.com/0122027/>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [collections] pairs package name
Posted by Neil O'Toole <ne...@yahoo.com>.
We could just put them in the o.a.c.collections package?
>neil
--- Stephen Colebourne <sc...@btopenworld.com> wrote:
> The pairs package name is perhaps not quite right. I would like the
> package
> to hold all non-collection data structure:
> - MapEntry
> - KeyValue
> - MultiKey
>
> How about renaming the package to data?
> (no backwards compatability issues)
>
> Stephen
>
>
> ---------------------------------------------------------------------
> 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