commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Colebourne" <scolebou...@btopenworld.com>
Subject Re: [primitives] Open for business
Date Sat, 06 Sep 2003 11:03:49 GMT
With collections, the only item that can cause problems is the RandomAccess
interface. This was added in JDK1.4, and not using it can slow down searches
and sorts. So a pre-1.4 and 1.4 onwards jar is something that should (in
theory) be done. Of course [collections] itself doesn't even do this.

Will 1.5 help primitives. Personally I doubt it, but who knows. The only
thing that might make a big difference is if it introduced factories for
Byte, Short and Integer where only one object was created in the JVM and
reused.

Whatever we do here, 1.2 must be the minimum JDK version we support. Too
many people still use it.

Stephen

----- Original Message -----
From: "__matthewHawthorne" <mhawthorne@alumni.pitt.edu>
To: "'Jakarta Commons Developers List'" <commons-dev@jakarta.apache.org>
Sent: Wednesday, September 03, 2003 3:36 AM
Subject: RE: [primitives] Open for business


> I've experienced the same situation, my last project had to run on Java
> 1.3 with no chances of getting 1.4.  I would imagine that there are
> plenty of production environments without the ability to upgrade to the
> newest versions, for one reason or another.
>
> I think it makes sense to attempt to support as many users and versions
> as possible, but there must be limits somewhere.  I think staying 1
> version behind the latest would be a good step, but commons would lose
> the ability to be used in Ant, for example, which targets 1.2.
>
> It may be overkill, but would it ever be possible to consider creating
> different branches of the code base for different Java versions?  If
> something we're implementing is also implemented in Java 1.5... it would
> be nice to get a version built for 1.5 which would possibly be faster
> and easier to manage, using the built-in features instead of ours.
>
> This may be a good idea, or a terrible one which creates unnecessary
> complexity.  I'm not sure.  I believe that Tomcat creates releases for
> 1.4 and pre-1.4 versions, but I'm not sure what the reasons behind it
> are.
>
>
>
>
> On Tue, 2003-09-02 at 10:50, Gary Gregory wrote:
> > Over here, we'd be lucky just to get off 1.3.1 and on to 1.4, forget
about
> > 1.5. :-( Our Java requirements are based on what the most common version
of
> > IBM WebSphere our customers run, which is the version that runs on
1.3.x. It
> > is a pain but our reality.
> >
> >
> > So including/not including 1.4 or 1.5-like features in the commons is
not
> > something /I/ think about beyond the desire that such feature be nicely
> > packaged and upgradeable (or at least documented) to the JRE version.
> >
> > Gary
> >
> > > -----Original Message-----
> > > From: Yoav Shapira [mailto:yoavs@apache.org]
> > > Sent: Monday, September 01, 2003 19:49
> > > To: Jakarta Commons Developers List
> > > Subject: Re: [primitives] Open for business
> > >
> > > Howdy,
> > > I may have missed the original discussion, but is primitives going to
have
> > > much of a market given the relative proximity of JDK 1.5 with its
> > > autoboxing features?  Or are there a bunch of features planned that
aren't
> > > going to be in JDK 1.5 anyways?
> > >
> > > Yoav Shapira
> > >
> > > On Tue, 2 Sep 2003, Stephen Colebourne wrote:
> > >
> > > > The [primitives] project has been created and is now ready for
> > > discussion,
> > > > debate and coding.
> > > >
> > > > At present, I have NOT removed anything from [collections]. I
believe
> > > that
> > > > there may be people with dependencies on the primitive code there. I
do
> > > not
> > > > plan to release that code however, nor will its prescence block a
> > > > [collections] release. I think that this will probably be the
position
> > > until
> > > > [primitives] is ready.
> > > >
> > > > So... lets try to get [primitives] sorted ;-)
> > > >
> > > > 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
>


Mime
View raw message