vladimir.kirichenko at gmail.com
Sat Nov 21 12:48:23 PST 2009
Rémi Forax wrote:
> I haven't survive to enum :)
> Since 1.0, JDK embeds a class named java.util.Enumeration,
> you can easily guess the name of the variable commonly used for that type.
AFAIU the biggest problems with new keyword is a package name or class
name. Big problem was with org.apache.commons.enum AFAIR.
If your moving your sources to next java version with all the language
improvements - changing the couple of local variables is not a big deal.
Remember migration to generics - that was a big peace of work.
Anyway with appearance of closures most people are going to be so happy
that this problems are going to be like a byte of small mosquito. And
anyway it's better than avoiding keywords with replacing them with
cryptic hieroglyphs. It's a change not for one day - it is how language
will going to look like within 5 years an later.
Another good example is C#. MS does not hesitate to add keywords to the
language and it does not seem that anyone get hurt much because of this.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 259 bytes
Desc: OpenPGP digital signature
Url : http://mail.openjdk.java.net/pipermail/closures-dev/attachments/20091121/77f7ed9c/attachment.bin
More information about the closures-dev