You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Bryce L Nordgren <bn...@fs.fed.us> on 2006/06/07 22:05:40 UTC

Collections-events

>Commons-collections is too big. It was deliberately
>broken out to make both parts managable.

>This project did have quite an active life at first.
>Where it floundered was that there were IIRC three
>competing code implementations (not just designs). I
>believe that all are currently in SVN. To revive this,
>we would have to select one without excessive ego.

I'm not sure I'm looking at the same package.  I see 25 classes, 30 tops.
There doesn't seem to be any overlap (e.g. two concepts coded in competing
ways).  And when it's compiled, the jar is 35k.  (less than 10% of
commons-collections, which weighs in at 500k--and commons-events depends on
commons-collections to boot).

>I also believe that Michael Heuer may have released
>something related on java.net?

Cool.  I'll go looking for it too.

Bryce


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Re: Collections-events

Posted by Stephen Colebourne <sc...@btopenworld.com>.
Bryce L Nordgren wrote:
>>Commons-collections is too big. It was deliberately
>>broken out to make both parts managable.
> 
>>This project did have quite an active life at first.
>>Where it floundered was that there were IIRC three
>>competing code implementations (not just designs). I
>>believe that all are currently in SVN. To revive this,
>>we would have to select one without excessive ego.
> 
> I'm not sure I'm looking at the same package.  I see 25 classes, 30 tops.
> There doesn't seem to be any overlap (e.g. two concepts coded in competing
> ways).

See 
http://mail-archives.apache.org/mod_mbox/jakarta-commons-dev/200306.mbox/%3c007801c32d17$3fdaafa0$083b29d9@oemcomputer%3e
for some discussion. There will be more before this, and a little after.

 > And when it's compiled, the jar is 35k.  (less than 10% of
> commons-collections, which weighs in at 500k--and commons-events depends on
> commons-collections to boot).
Yes its a small increase, but there seems to be a trend to favouring 
smaller jar files, particularly as they can be released more frequently.

Stephen

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Re: Collections-events

Posted by Bryce L Nordgren <bn...@fs.fed.us>.

Stephen Colebourne <sc...@btopenworld.com> wrote on 06/08/2006
01:29:25 AM:

> > I would be willing to help revive collections-events if there is
interest.
> > Even more so if it can happen with generics support.
>
> Logically, this would be a generics only project now. Does this affect
> you Bryce? (If it does, then perhaps we might need to try retro*)

I could go either way.  I'd be biased towards keeping it 1.4 just because I
don't think Generics adds anything to this particular block of code.  How
would you even use Generics with ObservableCollection/Set/Map/List?  If
there's a legitimate use of generics within the package, I may be
convinced.  Generics seems more applicable to commons-collections.

Jeez, you start porting commons-collections to generics and you've suddenly
got an awful lot of overlap with Java5 SE.  You've got a really good thing
going on here with your implementation!  You have a typed collections
framework which does not require a JVM change.  Furthermore, if you do use
a java 5 sdk targeted to java1.4, your type-checking still works (unlike
the J2SE package).  Why would you want to change that and become redundant?

But the best reason to stay at 1.4, at least for now: it seems to already
work!  I really don't understand why this was mothballed.  Might it be
released as 0.1 in its current state, then refactored to 1.5 in the next
release?

On the other hand, I don't have a good grasp of why one would use generics
at all, especially at the cost of breaking compatibility with many existing
systems.  Take it with a grain of salt. :) Now if it was a full-up template
facility, I could see using it.

Bryce


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Re: Collections-events

Posted by Stephen Colebourne <sc...@btopenworld.com>.
Michael Heuer wrote:
> Bryce L Nordgren wrote:
>>>I also believe that Michael Heuer may have released
>>>something related on java.net?
> 
> Sorry for chiming in late, my stuff is in cvs at java.net but was never
> released.
> 
> I would be willing to help revive collections-events if there is interest.
> Even more so if it can happen with generics support.

Logically, this would be a generics only project now. Does this affect 
you Bryce? (If it does, then perhaps we might need to try retro*)

Stephen

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Re: Collections-events

Posted by Michael Heuer <he...@acm.org>.
Bryce L Nordgren wrote:

> >I also believe that Michael Heuer may have released
> >something related on java.net?
>
> Cool.  I'll go looking for it too.

Sorry for chiming in late, my stuff is in cvs at java.net but was never
released.

I would be willing to help revive collections-events if there is interest.
Even more so if it can happen with generics support.

   michael


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org