------------
* <http://www.orionhealth.com>*
*Stephen Kestle Software Engineer*
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
P: +64 9 638 0619
M: +64 27 453 7853
F: +64 9 638 0699
S: skestle
www.orionhealth.com <http://www.orionhealth.com>
[EMAIL PROTECTED] wrote:
What about Collections?
Yeah - at the moment Stephen Colebourne and I are the only comitters.
He's busy working on a JSR and some other stuff, and I've had some
medical setbacks in the family that mean young children have been handed
around somewhat. It's looking
p://www.orionhealth.com>*
*Stephen Kestle Software Engineer*
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
P: +64 9 638 0619
M: +64 27 453 7853
F: +64 9 638 0699
S: skestle
www.orionhealth.com <http://www.orionhealth.com>
This e-mail and any attachments are intended only for the p
Good patch - seems I need to update my compiler warnings a bit.
Nice to get to 100% - one thing that interested me about that was
testing the extension of CollectionUtils. People - please see
https://issues.apache.org/jira/browse/COLLECTIONS-276.
And while CollectionUtils is updated for generic
// assume our implementation is correct if it returns the same order
as the Java function
+Collections.reverse(collectionA);
+assertEquals(collectionA, Arrays.asList(a));
+}
+
/**
* Records the next object returned for a mock iterator
--
---
IONS-245:
--------
I know Stephen Kestle is doing some work on the CollectionUtils. Are these
patches more complete? Would it help if I downloaded them, applied them, and
then reuploaded a patch file?
Genericise CollectionUtils and ListUtils.
-
But can't the library be first moved to a point where one can say the
new releases will run only on 1.5+ JVM, and then
gradually/slowly/carefully re-work/generify the internals as necessary
? So at least this won't constrain any new development effort from
using all the goodies in 1.5+, and yet
TED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
--------
* <http://www.orionhealth.com>*
it seems more descriptive of what you're doing. If it were toMap,
I wouldn't expect the input map to be there at all. The transformer
type parameters would give you enough type safety and you could just
instantiate a HashMap or something to return it.
On 9/2/07, Stephen Kestle &l
econd signature only has as there is no value transformer, so
the input collection is the type of value.
Cheers
Stephen
James Carman wrote:
What is "Map" here? The Map interface only has two type
parameters, right? Shouldn't it just be Map?
On 8/29/07, *Stephen Kestle * <[EM
.
Kind regards,
John Hunsley.
Technical Supervisor, Cy-nap Ltd.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Orion Signature
11 matches
Mail list logo