Community
Participate
Working Groups
When a private field is not referenced in a class, and is only referenced from ITDs, the compiler adds a warning on this field saying that the field is never read locally. Would be nice if this warning didn't exist. Seems that since the compiler has full access to the byte code of the class, it should know that the field is actually read.
i think there are a whole bunch of these, but as 1.6.4 is looking a bit itd themed, lets tackle this one.
unsetting the target field which is currently set for something already released