Return-Path: Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 96534 invoked from network); 28 Aug 2003 06:11:35 -0000 Received: from unknown (HELO protactinium.btinternet.com) (194.73.73.176) by daedalus.apache.org with SMTP; 28 Aug 2003 06:11:35 -0000 Received: from host81-128-120-46.in-addr.btopenworld.com ([81.128.120.46] helo=oemcomputer) by protactinium.btinternet.com with smtp (Exim 3.22 #23) id 19sG0X-0002eU-00 for commons-dev@jakarta.apache.org; Thu, 28 Aug 2003 07:11:45 +0100 Message-ID: <001f01c36d2b$91ca9560$2e788051@oemcomputer> From: "Stephen Colebourne" To: "Jakarta Commons Developers List" References: <005701c36ced$3eb05ba0$2f428051@oemcomputer> <3F4D41E7.9030104@alumni.pitt.edu> <3F4D4278.8010105@comcast.net> <3F4D454F.3010107@alumni.pitt.edu> Subject: Re: [pcollections][PROPOSAL] Primitive collections - new sandbox component from [collections] Date: Thu, 28 Aug 2003 07:13:58 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ----- Original Message ----- From: "__matthewHawthorne" > Java 1.5 is going to have a lot of new tricks, such as the auto boxing > and unboxing that you're referring to, also generics, enums, etc. I've > played with the prototype compiler, and I have to say, the new features > are pretty cool. It seems that a lot of the things they are providing > have been implemented in some way already in commons. Yes commons is sometimes what I call 'Next Generation Java'. However primitive collections are NOT going into 1.5, autoboxing is. The difference is a large amount of performance and memory space. (Autoboxing will store a 'primitive' list using wrapper classes like Integer. [pcollections] uses an internal int[] - big difference) > It appears to be a requirement that all commons code must run on Java > 1.2, but I'm not quite sure why. Why is this? Maybe comons should > always stay 2 versions behind the current Java version, and bump up to > 1.3 once 1.5 comes out... is this possible or desirable? If we can run on 1.2, why not? Stephen > Another example is Ant... until recently, I think Ant was still required > to run on Java 1.1, but they bumped it up to Java 1.2 for Ant 1.6. > They've just started using Collections... it seems kind of strange. > > > > > Sean W. Ferguson wrote: > > > Isn't Java 1.5 going to have this? > > > > __matthewHawthorne wrote: > > > >> Sounds great, as there is already a large codebase to get started with. > >> > >> pcollections seems like a nice simple name... primitive-collections > >> seems too long, and other combinations of half-words like "prim" and > >> "coll" may just leave people confused. > >> > >> I'm willing to lend a helping hand... just let me know where to aim > >> and shoot. > >> > >> > >> > >> > >> Stephen Colebourne wrote: > >> > >>> The attached proposal is to create a new Sandbox project, named > >>> [pcollections] to house a complete set of primitive collections. > >>> Reasoning: > >>> > >>> 1) [collections] is already large, and primitive-collections and > >>> collections > >>> actually have remarkably little in common > >>> > >>> 2) The current primitive collections code in [collections] is > >>> completely > >>> isolated from the rest of the [collections] code, a sure-fire > >>> indicator of > >>> being better in a separate project with its own release cycle > >>> > >>> 3) A positive response from Soren Bak of the PCJ project to integrate a > >>> complete set of primitive-collections together in one place. > >>> > >>> > >>> This mail is to enable anyone to > >>> - object to the idea > >>> - come up with a better name than pcollections > >>> - to volunteer support (please!!) > >>> - or any other comment :-) > >>> > >>> 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 > >> > >> > > > > > > --------------------------------------------------------------------- > > 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 >