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/09 22:12:07 UTC
[pcollections] Name change?
Should we name it [pcollections]? Or is [primitives] better? (The sandbox
primitives is then a sandbox for the proper component for experimentation).
I had forgotten about the special io input stream stuff, which might lead to
the name [primitives]. I don't think that this affects the vote, but it does
affect the CVS creation!
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [pcollections] Name change?
Posted by Dirk Verbeeck <di...@pandora.be>.
+1 to primitives
Stephen Colebourne wrote:
>Should we name it [pcollections]? Or is [primitives] better? (The sandbox
>primitives is then a sandbox for the proper component for experimentation).
>
>I had forgotten about the special io input stream stuff, which might lead to
>the name [primitives]. I don't think that this affects the vote, but it does
>affect the CVS creation!
>
>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] Name change?
Posted by Stephen Colebourne <sc...@btopenworld.com>.
I've adapted the proposal slightly for the name change, with an extra
descriptive paragraph, and less emphasis on collections. Any changes needed?
I'll include the final text in the vote result and give people a chance to
object.
Stephen
------
(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 utilities and collections
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.
------
----- Original Message -----
From: "Rodney Waldhoff" <rw...@apache.org>
> +1 to the name "primitives" over "pcollections"
>
> On Thu, 9 Oct 2003, Stephen Colebourne wrote:
>
> > Should we name it [pcollections]? Or is [primitives] better? (The
sandbox
> > primitives is then a sandbox for the proper component for
experimentation).
> >
> > I had forgotten about the special io input stream stuff, which might
lead to
> > the name [primitives]. I don't think that this affects the vote, but it
does
> > affect the CVS creation!
> >
> > Stephen
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> >
>
> --
> - Rod <http://radio.weblogs.com/0122027/>
>
> ---------------------------------------------------------------------
> 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] Name change?
Posted by Rodney Waldhoff <rw...@apache.org>.
+1 to the name "primitives" over "pcollections"
On Thu, 9 Oct 2003, Stephen Colebourne wrote:
> Should we name it [pcollections]? Or is [primitives] better? (The sandbox
> primitives is then a sandbox for the proper component for experimentation).
>
> I had forgotten about the special io input stream stuff, which might lead to
> the name [primitives]. I don't think that this affects the vote, but it does
> affect the CVS creation!
>
> Stephen
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
--
- Rod <http://radio.weblogs.com/0122027/>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[collections] package observed --> observable
Posted by Michael Heuer <he...@acm.org>.
While I'm at giving my thoughts on names for things, I would also like to
see the package o.a.c.collections.observed change to observable to match
the class names. I can submit a patch if desired, but most of the change
is in cvs, not in the source code.
michael
On Thu, 9 Oct 2003, Michael Heuer wrote:
>
> For what it's worth, I much prefer using the name [primitives] to
> [pcollections].
>
> (non-binding) +1
>
> michael
>
>
> On Thu, 9 Oct 2003, Stephen Colebourne wrote:
>
> > Should we name it [pcollections]? Or is [primitives] better? (The sandbox
> > primitives is then a sandbox for the proper component for experimentation).
> >
> > I had forgotten about the special io input stream stuff, which might lead to
> > the name [primitives]. I don't think that this affects the vote, but it does
> > affect the CVS creation!
> >
> > 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] Name change?
Posted by Michael Heuer <he...@acm.org>.
For what it's worth, I much prefer using the name [primitives] to
[pcollections].
(non-binding) +1
michael
On Thu, 9 Oct 2003, Stephen Colebourne wrote:
> Should we name it [pcollections]? Or is [primitives] better? (The sandbox
> primitives is then a sandbox for the proper component for experimentation).
>
> I had forgotten about the special io input stream stuff, which might lead to
> the name [primitives]. I don't think that this affects the vote, but it does
> affect the CVS creation!
>
> 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] Name change?
Posted by Henri Yandell <ba...@generationjava.com>.
+1 to primitives. It has superb logo potential :)
On Thu, 9 Oct 2003, Stephen Colebourne wrote:
> Should we name it [pcollections]? Or is [primitives] better? (The sandbox
> primitives is then a sandbox for the proper component for experimentation).
>
> I had forgotten about the special io input stream stuff, which might lead to
> the name [primitives]. I don't think that this affects the vote, but it does
> affect the CVS creation!
>
> 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