Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 36718 invoked from network); 14 Oct 2002 12:32:53 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 14 Oct 2002 12:32:53 -0000 Received: (qmail 14984 invoked by uid 97); 14 Oct 2002 12:33:37 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 14962 invoked by uid 97); 14 Oct 2002 12:33:36 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 14942 invoked by uid 98); 14 Oct 2002 12:33:35 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Date: Mon, 14 Oct 2002 08:32:45 -0400 (EDT) From: Henri Yandell X-X-Sender: To: Jakarta Commons Developers List Subject: Re: [lang] Ideas for Lang In-Reply-To: <5.1.0.14.0.20021014143202.043798b8@pop.scioworks.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Mon, 14 Oct 2002, John Yu wrote: > > > > 4) Pair. Is this Collections? Dunno. Anyway, pairs seem to be nice > > > > sometimes. I only have one because I was porting the lisp examples > > to Java > > > > from the lisp book [yep, i'm that sick]. > > > > > > Isn't o.a.c.collections.DefaultMapEntry, fulfilling the role of Pair? > > > >Possibly, though it isn't semantically. Assuming there's a need for a Pair > >class, using DefaultMapEntry would not fulfill it, even if the > >functionality were the same. > > > >My vague view being that things can be syntactically the same but > >semantically different. > > > You lost me. > Could you elaborate? What semantics you're referring to in Pair? Erm.. pass? :) I was hoping there might be a good Lisp fanatic or something with some reasons for why a Pair object would be very useful. I seem to recall reading someone's blog opining for a Pair class. The semantic bit was... I think there are many places where someone would like to use a Pair and not a DefaultMapEntry. ie) They're not dealing with Map.Entry functionality. [One of the dangerous parts of suggesting ideas you don't believe in a lot yourself :) ] Similar for the Mutable-primitives. I often find a point in code where I think, "wish I could set the Integer", but then I get around it somehow without much effort. Hen -- To unsubscribe, e-mail: For additional commands, e-mail: