[ https://issues.apache.org/jira/browse/COLLECTIONS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648194#action_12648194
]
Donal Murtagh commented on COLLECTIONS-110:
-------------------------------------------
I think one person's dislike of generics is not a sufficiently good reason for rejecting this
request. Although many/most people feel that the Java implementation of generics is not ideal,
on balance, I believe that most people feel it's better than no generics at all. For example,
I don't know of any projects that are using Java 1.5+ but don't actually use generics.
Anyway, it seems like this issue is dead, but in case it is resurrected, I would emphatically
support a generic version of this library even if it is not 100% backward compatible, or uses
different package names so that it can co-exists with a non-generic version,
> Support parametized classes with commons.collections.
> -----------------------------------------------------
>
> Key: COLLECTIONS-110
> URL: https://issues.apache.org/jira/browse/COLLECTIONS-110
> Project: Commons Collections
> Issue Type: Wish
> Environment: Operating System: other
> Platform: Other
> Reporter: Colbert Philippe
> Assignee: Stephen Kestle
> Fix For: Generics
>
> Attachments: collections.patch, Jakarta Collections-generic.tar.gz
>
>
> It's time to create a parallel version of commons.collections to support
> parametized classes of each container class and abstract class. It's not that
> hard. There is a 23 PDF document on Sun Java website describing in detail how
> it should be done and what to watch out for.
> I already converted a few classes from commons.collection privately for my own
> needs. Once you get the hang of it, it's a rather quick process.
> I am even willing to volunteer my time to do some more but I need the
> collaboration of some of the original programmers to watch over things.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
|