Hi Hackers,
I just want to call your attention to an issue that may cause some
headaches in the future if we fail to prevent them now.
In the JDK 1.5 Tiger release, "enum" is a reserved word to define
enumerated types, similar to those in C++.
However, in JDKs < 1.5, it was common to use the name enum when
enumerating over object collections. For example,
for (Enumeration enum = zipFile.entries(); enum.hasMoreElements();) {
...
}
To prevent compile errors when we eventually migrate to JDK 1.5, I
suggest that we adopt the convention of naming our enumerators "en"
instead of "enum". We have reserved "i" for Iterators and "e" for
Exceptions, so I think "en" is a logical progression.
Also, for a more urgent motivation, the current release of LOCC is based
upon the JDK 1.5 grammar and treats "enum" as a reserved word. This
means whenever we name a variable "enum", LOCC will fail to parse the
file and we will not have FileMetric data for that module until it is fixed.
Thanks for your help. Happy hacking!
Mike
