Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 20931 invoked from network); 19 Aug 2002 18:18:38 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 19 Aug 2002 18:18:38 -0000 Received: (qmail 10889 invoked by uid 97); 19 Aug 2002 18:19:04 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 10851 invoked by uid 97); 19 Aug 2002 18:19:04 -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 10826 invoked by uid 98); 19 Aug 2002 18:19:03 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <20020819181835.69499.qmail@web21203.mail.yahoo.com> Date: Mon, 19 Aug 2002 11:18:35 -0700 (PDT) From: Jonathan Carlson Reply-To: joncrlsn@users.sf.net Subject: RE: [Collections] Release potential? To: Jakarta Commons Developers List In-Reply-To: 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 I'm sorry to bring these things up at a rather late date but I guess it's better now than after the release. 1) It would be nice to have better class documentation on the "primitive" package classes. It is unobvious to me (looking at the API) what using IntArrayList would "buy" me other than no ClassCastExceptions. Is it faster or does it use less memory or something else or neither? The API should be obvious without having to look at the code. 2) ArrayList is a specific implementation that should not be used in the name of these classes (AbstractIntArrayList and IntArrayList) because it implies a certain implementation (namely the use of ArrayList or subclass of it) that isn't the case. The differences (ArrayList of Integers vs. arrays of ints) are very important in terms of memory usage (see http://www.javaworld.com/javaworld/javatips/jw-javatip130.html). 3) I would greatly prefer to have an IntList interface so I can declare variables and arguments with an interface instead of an abstract super class (like we do with the collection interfaces). See Joshua Bloch's "Effective Java" item number 16 on page 84. He agrees with me too. Does anyone else see this the way I do? I'd be happy to commit documentation improvements (#1), but I don't think I am known enough to get approved. (I wrote the TransformingComparator class which I think IMHO is pretty well documented). Jonathan --- "Jack, Paul" wrote: > > I'm a big fan of having the release notes completed > prior to > > a release. The release vote then is a simple "these > exact > > bits are what we are releasing" rather than some > unknown product... > > Ok, I'll work on the release notes then. > > > > It seems like everything has been addressed, but I'd > like to take a > > closer look over my todo list. Unfortunately, I won't > have > > time until at least Saturday. > > Ok. > > > > Does this also mean you're volunteering to be the > release manager for > > the release? :) > > I guess so. Why not bring my compulsive obsessions with > the Collections > API to their natural end... > > -Paul > > > -- > To unsubscribe, e-mail: > > For additional commands, e-mail: > > ===== Jonathan Carlson joncrlsn@users.sf.net Minneapolis, Minnesota __________________________________________________ Do You Yahoo!? HotJobs - Search Thousands of New Jobs http://www.hotjobs.com -- To unsubscribe, e-mail: For additional commands, e-mail: