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/10/10 10:01:26 UTC

[RESULT] and possible revote - Re: [VOTE] New commons proper component - pcollections

If you voted, please read!

The vote to create pcollections succeeded. However after a little further
discussion, the name [primitives] has been preferred. The amended charter
is:
------
(0) Rationale

The Java language has a fundamental distinction between Object and primitive
types. The JDK provides many method for manipulating and working with
Objects. However, there is relatively little support for working with
primitive types.

One key example is the Java Collection Framework. This defines a well-known
and widely used API for object-based collections. The framework requires
each primitive to be wrapped in an object, such as Integer, before they can
be used in collections. This has a memory and performance overhead.

The primitives component will provide an API for collections and utilities
based on primitives. Wrappers and adaptors will be provided for integration
with object-based APIs.

(1) Scope of the Package

The package will create and maintain a set of collections and utilities for
primitive types, distributed under the ASF license.
------
If anyone wants to object, or call a revote, please feel free. Otherwise I
will take this as accepted based on the original vote :-)
Stephen

----- Original Message -----
From: "Stephen Colebourne" <sc...@btopenworld.com>
> The [collections] component has been housing unreleased, but stable
> primitive collections code for some time. These are collections that store
> primitive arrays behind the scenes instead of objects. (Note that JDK1.5
> does NOT address the need for these classes).
>
> Following discussion within the [collections] component on the best
release
> strategy, we would like to create a new commons-PROPER component to house
> the code. The aim is to give this useful code room to grow without
impacting
> the widely used main [collections] (object-based) component.
>
> It is important to emphasise that this is not new code - it is stable and
> ready for release. Thus commons-proper, rather than the sandbox, is the
> appropriate place for the new component.
>
> The proposal is attached for the new component 'pcollections'. (No one
likes
> this name, but we haven't found a better one).
>
> Please vote as to whether you support this new commons-PROPER component.
> [  ] +1  Yes, lets create [pcollections]
> [  ] +0
> [  ] -0
> [  ] -1  No, I oppose this because....
>
> 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