Nico Klasens wrote: > A little late, but I was just too busy with other things. > > imo a major release is justified when we do a good implemtation of java > 5. The api will change drasticly which makes it impossible to create a > drop-in replacement. > A good implementation should remove many of our convenience classes in > the bridge. E.g. a NodeList should just become List<Node> and not > NodeList<Node> I played around with this at the component weekend and > realized that it is impossible at the moment. The NodeList > implementation does also some conversion of objects. You can add any > object to the list and the NodeList will try to convert it to a Node. A > good discussion on the API is required I think.
I agree that it would be actually better to drop all List interfaces from bridge. But I am uncertain if something like that can be done, because it is obviously backwards incompatible. A thing which is, very in the bridge, undesirable. I see other options: - leave it (approximately) as is. NodeList<Node> is a sillyness, but you don't need to use it. You can still write simply NodeList. - roll it back. We simply don't support generics in bridge. Because of prior choices, that proves to be an impossibility. One can fear that stalling the release until a good discussion has taken place, may stall it a bit long. But anyhow those were my first 2c.. :-) On the other hand, '2.0' is only an arbitrary marker. Its main goal would be to sound better than '1.9'. It is not necessarily a mayor backwards compatibility break. If we want to do that later, we can also call it 3.0 or 4.0. There's plenty of room in that direction. Michiel -- Michiel Meeuwissen mihxil' Peperbus 107 MediaPark H'sum []() +31 (0)35 6772979 nl_NL eo_XX en_US _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
