commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Carman <ja...@carmanconsulting.com>
Subject Re: [all] Core library dependencies [was COLLECTIONS 3.3 release]
Date Tue, 12 May 2009 15:29:21 GMT
On Tue, May 12, 2009 at 7:29 AM, Stephen Colebourne
<scolebourne@btopenworld.com> wrote:
> The 'functors' in [collections] and [functor] are very different:
> http://commons.apache.org/collections/api-release/org/apache/commons/collections/package-summary.html
> http://commons.apache.org/sandbox/functor/apidocs/org/apache/commons/functor/package-summary.html
> There is no need to share these interfaces, add dependencies or anything similar. (Equally,
were they the same John's argument would be sound.)

I would argue that they're not inherently different, though.  A
Predicate in collections-speak is the same thing as a UnaryPredicate
in functor-speak.  They are interfaces that have one method taking an
object (of a particular type in the "new" stuff) and returns
true/false.  Likewise, a Closure is a UnaryProcedure and a Transformer
is a UnaryFunction.  There really should be no need to come up with a
new concept here, IMHO.  What's wrong with having a very simple API
jar from functor (which includes the no-arg, unary, and binary
versions of the three interfaces)?  These interfaces haven't changed
(nor can they by definition) for a long time aside from us now adding
generics to the mix, but that's a non-issue since we're talking about
making these changes in the generified collections library.

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


Mime
View raw message