On Tue, Apr 12, 2011 at 1:36 PM, Paul Benedict wrote:
> I think "tuple" is a better package name. In geo-coordinates, I don't think
> it's proper to call Longtitude a key and Latitude a value. It's just a tuple
> of values. Same thing for 3d dimension space, etc.
>
>
> On Tue, Apr 12, 2011 at 12:
I think "tuple" is a better package name. In geo-coordinates, I don't think
it's proper to call Longtitude a key and Latitude a value. It's just a tuple
of values. Same thing for 3d dimension space, etc.
On Tue, Apr 12, 2011 at 12:33 PM, Gary Gregory wrote:
> On Tue, Apr 12, 2011 at 12:16 PM, Ste
On Tue, Apr 12, 2011 at 12:16 PM, Stephen Colebourne
wrote:
> On 12 April 2011 17:10, Matt Benson wrote:
> > On Tue, Apr 12, 2011 at 10:20 AM, Stephen Colebourne
> > wrote:
> >> The [collections] KeyValue class was a mistake. [lang] Pair is a
> >> better more general concept.
> >>
> >> The only
On 12 April 2011 17:10, Matt Benson wrote:
> On Tue, Apr 12, 2011 at 10:20 AM, Stephen Colebourne
> wrote:
>> The [collections] KeyValue class was a mistake. [lang] Pair is a
>> better more general concept.
>>
>> The only thing I'd consider with [lang] Pair now is whether it should
>> move to its
On Tue, Apr 12, 2011 at 10:20 AM, Stephen Colebourne
wrote:
> The [collections] KeyValue class was a mistake. [lang] Pair is a
> better more general concept.
>
> The only thing I'd consider with [lang] Pair now is whether it should
> move to its own package, in case it grows later (primitive versi
The [collections] KeyValue class was a mistake. [lang] Pair is a
better more general concept.
The only thing I'd consider with [lang] Pair now is whether it should
move to its own package, in case it grows later (primitive versions).
Stephen
On 11 April 2011 21:00, Matt Benson wrote:
> On Mon,
On Mon, Apr 11, 2011 at 1:31 PM, Gary Gregory wrote:
> Hi All:
>
> I am now realize that what we are stumbling along with Pair has already been
> done in org.apache.commons.collections.keyvalue, generics and all. Different
> class names but the same ideas.
>
> So... it sure would be nice to avoid
Drop keyvalue in favour of Pair? :)
More seriously; keep Pair (or keyvalue if that's a better name) in
Lang, and make Collections depend on Lang for the core pair concept.
Hen
On Mon, Apr 11, 2011 at 11:31 AM, Gary Gregory wrote:
> Hi All:
>
> I am now realize that what we are stumbling along w
Hi All:
I am now realize that what we are stumbling along with Pair has already been
done in org.apache.commons.collections.keyvalue, generics and all. Different
class names but the same ideas.
So... it sure would be nice to avoid creating the same thing in [lang] but
with different class names.
