RE: [collections] [functor] Split functors from collections

2005-11-25 Thread robert burrell donkin
On Thu, 2005-11-24 at 20:09 -0500, James Carman wrote: > I would agree that merging the functors from collections into commons > functor would not work (Transformer vs. UnaryFunction for example). My only > point would be that if we're trying to create a general-purpose functor > library (what com

RE: [collections] [functor] Split functors from collections

2005-11-24 Thread James Carman
ssage- From: Stephen Colebourne [mailto:[EMAIL PROTECTED] Sent: Thursday, November 24, 2005 7:43 PM To: Jakarta Commons Developers List Subject: Re: [collections] [functor] Split functors from collections If you'd like to compare functor sandbox and collections-functor I think you'll

Re: [collections] [functor] Split functors from collections

2005-11-24 Thread Stephen Colebourne
or example). -Original Message- From: Stephen Colebourne [mailto:[EMAIL PROTECTED] Sent: Thursday, November 24, 2005 6:58 PM To: Jakarta Commons Developers List Subject: Re: [collections] [functor] Split functors from collections Does it actually need a deprecation release? The new comp

RE: [collections] [functor] Split functors from collections

2005-11-24 Thread James Carman
). -Original Message- From: Stephen Colebourne [mailto:[EMAIL PROTECTED] Sent: Thursday, November 24, 2005 6:58 PM To: Jakarta Commons Developers List Subject: Re: [collections] [functor] Split functors from collections Does it actually need a deprecation release? The new component will have

Re: [collections] [functor] Split functors from collections

2005-11-24 Thread Stephen Colebourne
Does it actually need a deprecation release? The new component will have the same classes in the same packages. The only difference is that users will need to pickup another jar. In fact, since this is the case, deprecation will actually cause confusion to users. Depending on which is first in

Re: [collections] [functor] Split functors from collections

2005-11-24 Thread Dion Gillard
+1 to the split. Proposal A would seem to make the most sense. I'd like to see a 'deprecation release' of collections with the functor code marked as deprecated so that users know this is being moved. This would give be a big heads up about the new component and that their build process should c

RE: [collections] [functor] Split functors from collections

2005-11-24 Thread James Carman
What about the existing Commons Functor library? Collections should really use those as opposed to defining its own. I realize that Commons Functor came about after Collections, but if we're going to start splitting stuff out, maybe we should revive functor for this stuff and maybe start migratin

Re: [collections] [functor] Split functors from collections

2005-11-24 Thread Christian Meder
On Thu, 2005-11-24 at 21:52 +, Stephen Colebourne wrote: > Commons collections is a large jar file. Some users have issue with > that. Those users tend to complain most about the functor part, which is > an area of more religious feeling than the rest of collections. > > I want to float the