True enough that [functor] already contains *Function interfaces that
meet these requirements.
-Matt
On Dec 26, 2009, at 6:10 PM, Gary Gregory wrote:
Unless [lang] would use it internally all over the place. Is there
a case for that? How is the interface useful without parameters?
Gary
Missing file prevents site build. Another RC is necessary.
Phil
Phil Steitz wrote:
> Hopefully 3 is a charm here - I have cut a third release candidate
> and would like to reopen the release vote based on RC3. As
> previously discussed, the only difference between 1.3 and 1.4 is
> that the 1.3
Luc Maisonobe wrote:
> Luc Maisonobe a écrit :
>> Phil Steitz a écrit :
>>> Hopefully 3 is a charm here - I have cut a third release candidate
>>> and would like to reopen the release vote based on RC3. As
>>> previously discussed, the only difference between 1.3 and 1.4 is
>>> that the 1.3 source
Luc Maisonobe wrote:
> Phil Steitz a écrit :
>> Hopefully 3 is a charm here - I have cut a third release candidate
>> and would like to reopen the release vote based on RC3. As
>> previously discussed, the only difference between 1.3 and 1.4 is
>> that the 1.3 sources have been filtered to exclude
Luc Maisonobe a écrit :
> Phil Steitz a écrit :
>> Hopefully 3 is a charm here - I have cut a third release candidate
>> and would like to reopen the release vote based on RC3. As
>> previously discussed, the only difference between 1.3 and 1.4 is
>> that the 1.3 sources have been filtered to excl
Commons Proxy has an interface very much like the one you're
suggesting. I considered using Commons Functor's "Function" interface
instead.
On Sun, Dec 27, 2009 at 9:50 AM, Oliver Heger
wrote:
> The idea is related to some classes in the concurrent package that provide
> specific ways to create
Phil Steitz a écrit :
> Hopefully 3 is a charm here - I have cut a third release candidate
> and would like to reopen the release vote based on RC3. As
> previously discussed, the only difference between 1.3 and 1.4 is
> that the 1.3 sources have been filtered to exclude JDBC4 methods.
I don't kn
Hopefully 3 is a charm here - I have cut a third release candidate
and would like to reopen the release vote based on RC3. As
previously discussed, the only difference between 1.3 and 1.4 is
that the 1.3 sources have been filtered to exclude JDBC4 methods.
Here are the artifacts:
1.3 (JDBC 3) ve
The idea is related to some classes in the concurrent package that
provide specific ways to create objects, e.g. lazy creation or creation
in a background thread. If there was a standard factory interface
implemented by these classes, client code could directly make use of
these enhanced object
