Jon,
Sorry for the late reply. I've been away on business for a few days, so
am playing catch up. After the recent appearance of the
collections.sf.net project, there are now two projects that attempt to
provide a Java 5.0 port of commons-collections. Since the duplication of
work seems a
Hi all,
Sometime last summer, a there was a discussion about providing a generic
port of collections. The upshot was that no Apache commiters could
commit to providing time to handle this at Apache, and so I started the
collections15.sf.net project over on SourceForge. A lot of the issues
Hi Bryan,
After some discussions on the subject some time ago, it was decided that
collections should concentrate on maintaining supporting for earlier JDK
versions, whilst the Java 5.0 port should not carry over any Java 1.4
baggage and concentrate on providing the same functionality as
Ooops,
I thought I'd replied to the commons dev list, but Laurent's original
e-mail had an explicit reply-to address set, so it went straight back to
him instead. I'm posting this back to the commons-dev list for the sake
of completeness.
Chris
Hi Laurent,
After an initial flurry of activity
Hello Thomas,
You're right. There was a brief discussion about a Java 5.0 port of
collections. The upshot was the project that Michael has pointed out on
SourceForge. There are two people working on this at the moment - myself
and Mauro Franceschini. After an initial bout of work on this
Hi Lukas,
Whilst generic collections provide type safety at compile time, at
runtime all of the specific type information is erased and the
collections classes behave much the same way as their Java 1.4
predecessors. With respect to the actual implementations of the classes
within the Java
Works for me. Not a lot of traffic, though.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Stephen Colebourne wrote:
I am unsure as to the use case for a ReferenceList/ReferenceSet. We
already have ReferenceMap, which is very useful for building caches,
but why would you need a List/Set? How would they operate?
Well, here's an example, of the top of my head. A weakly referencing
list
Stephen Colebourne wrote:
I am unsure as to the use case for a ReferenceList/ReferenceSet. We
already have ReferenceMap, which is very useful for building caches,
but why would you need a List/Set? How would they operate?
Well, here's an example, off the top of my head. A weakly referencing
Bastian Helfert wrote:
Jakarta Commons Developers List commons-dev@jakarta.apache.org schrieb am
24.12.04 11:09:48:
Well, here's an example, of the top of my head. A weakly referencing
list could be useful for implementing the observer pattern in a
situation where you don't want the
Matt Sgarlata wrote:
Does this mean .NET doesn't have reflection? That's such a killer
feature of Java; I can't believe they wouldn't have ported it to .NET.
Any .NET developers out there that can tell us how .NET deals with
reflection when you have multiple versions of the same class?
Since
Someone suggested that for Log, it would be appropriate to make it an
abstract class rather than an interface, so we can make these kinds of
changes easier in the future. I think the risks for this are low, and
probably better [less problems for the majority of users] than just adding
new
Correct me if I'm wrong, but didn't Microsoft come up with some type
of solution to DLL hell in Windows 2000 or XP? I seem to recall
reading that a long time ago, but I'm not a Windows programmer, so I
have no idea. Does anyone else know?
The .NET equivalent of a jar file is called an
Emmanuel Bourg wrote:
Also the Class[] and Object[] are quite cumbersome, that would be nice
to add methods/constructors to invoke simple methods with only one or
two parameters. Thus my example could look like this:
CollectionUtils.forAllDo(configList, new
InvokerClosure(clearProperty,
Eric Pugh wrote:
Is the final result:
CollectionUtils.forAllDo(configList, new InvokerClosure(clearProperty,
String.class, key));
Compared to the original really that much cleaner?:
for (Iterator i = configList.iterator(); i.hasNext();)
{
Configuration config = (Configuration) i.next();
been screwed up.
If we really want such syntactic niceties, I reckon we just have to move
wholesale to Java 1.5, and accept the break in backwards compatibility.
Chris Lambrou
P.S. While I'm thinking about it, have there been any steps towards
migrating commons-lang to Java 1.5? Anyone
Actually, I misunderstood your original suggestion a little. It's quite
late here in England!
Emmanuel Bourg wrote:
What prevents the debugging of a library 1.3 compatible with a 1.5
source ? The line numbers don't match ?
Yeah, pretty much. But there are a number of other little things that
Hi,
As much as I'd like to replace all of the existing parameter checks with
assertions, I think that the current method of having explicit parameter
checking on all public methods will have to stand. Many thanks to you
all for your useful input. I thought that for the sake of completeness,
Hi,
Although I've marked the subject with [collections], I guess this is
targeted at anyone who has an interest in a Java 5.0 port of any jakarta
project. I'm slowly chipping away at a Java 5.0 port of
commons-collections. As I've been generifying the original collections
classes, I've found
Andre,
I've just checked out collections from scratch, and it all builds just
fine. I haven't seen any commits to CVS since your original message, so
I'm not entirely sure what's going wrong here, but hopefully this will
help you to pin down the problem.
Chris
A Leg wrote:
Hi
If I try to
Hi Michael,
Hello Chris,
I feel it would be best to implement collections + generics as a project
in the commonds sandbox. That way we get cvs, bugzilla, gump,
ibiblio/maven mirror, etc. support and lots of interested eyeballs on the
commons mailing list. But we would need an apache committer.
Hi,
I'm having trouble setting up CVS access to the Jakarta modules. I'm
trying to configure WinCVS as my CVS client, and I've followed the
instructions shown at http://jakarta.apache.org/site/cvsindex.html. All
appears to go well - the client successfully connects to the CVS
repository using
Martin,
As I said, I haven't used CVS much and wasn't aware of the distinction
between modules and repositories. It also didn't seem obvious to me
that the WinCVS gui allows one to type in any repository name, rather
than having to select one of the modules. Anyhow, it's all worked a
treat,
I thought I'd make a start on converting commons-collections to use
generics under the JDK 1.5. Before I go too far, I'd like to hear
peoples comments on the subject. In particular, I'd like to know what
people have to say about the following issues.
Project
From previous discussions on this
Agreed! I thought the whole point of the various commons libraries was
to provide a low-level set of libraries upon which other apps can be
built upon. Why then is it such a problem for the different commons
project themselves to be interdependent? I can understand not wanting
to have
25 matches
Mail list logo
