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/08/28 00:47:50 UTC
[pcollections][PROPOSAL] Primitive collections - new sandbox component from [collections]
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
Re: [pcollections][PROPOSAL] Primitive collections - new sandbox component from [collections]
Posted by Stephen Colebourne <sc...@btopenworld.com>.
----- Original Message -----
From: "__matthewHawthorne" <mh...@alumni.pitt.edu>
> 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
>
Re: [pcollections][PROPOSAL] Primitive collections - new sandbox
component from [collections]
Posted by Henri Yandell <ba...@generationjava.com>.
On Wed, 27 Aug 2003, David Graham wrote:
> --- __matthewHawthorne <mh...@alumni.pitt.edu> wrote:
> > It appears to be a requirement that all commons code must run on Java
> > 1.2, but I'm not quite sure why.
>
> This is not a requirement. Each project can choose what their minimum
> Java level is.
Dunno. Officially, Jakarta Commons exists to serve other Jakarta projects.
At the moment 1.2 is the minimum for most of these, but with a lot of the
servlet level ones going to 1.4, maybe we could consider doing that too.
Hen
Re: [pcollections][PROPOSAL] Primitive collections - new sandbox component from [collections]
Posted by David Graham <gr...@yahoo.com>.
--- __matthewHawthorne <mh...@alumni.pitt.edu> wrote:
> 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.
>
> It appears to be a requirement that all commons code must run on Java
> 1.2, but I'm not quite sure why.
This is not a requirement. Each project can choose what their minimum
Java level is.
David
> 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?
>
> 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
>
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
Re: [pcollections][PROPOSAL] Primitive collections - new sandbox
component from [collections]
Posted by __matthewHawthorne <mh...@alumni.pitt.edu>.
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.
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?
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
>
>
Re: [pcollections][PROPOSAL] Primitive collections - new sandbox component from [collections]
Posted by David Graham <gr...@yahoo.com>.
--- "Sean W. Ferguson" <se...@comcast.net> wrote:
> Isn't Java 1.5 going to have this?
Yes, Java 1.5's autoboxing of primitives gives you this functionality.
David
>
> __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
>
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
Re: [pcollections][PROPOSAL] Primitive collections - new sandbox
component from [collections]
Posted by "Sean W. Ferguson" <se...@comcast.net>.
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
>
>
Re: [pcollections][PROPOSAL] Primitive collections - new sandbox
component from [collections]
Posted by __matthewHawthorne <mh...@alumni.pitt.edu>.
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
>