Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.0-JSR-1
-
Fix Version/s: 1.0-JSR-4
-
Component/s: None
-
Labels:None
-
Environment:Eclipse 3.1M6, using 1.4 compiler settings and enabled many warnings
-
Number of attachments :
Description
See the attached "\t" separated file. It lists around 700 warnings Eclipse 3.1M6 (using 1.4 compiler settings and enabled many warnings) generates. Which ones are no-gos? Which are to be ignored?
I start a list here, sorting out the severity type of warning descriptions.
[ might be ignored ] (by Eclipse's and other compiler settings)
o Access to enclosing method getCurrent() from the type T is emulated by a synthetic accessor method. Increasing its visibility will improve your performance.
o Statement unnecessarily nested within else clause. The corresponding then clause does not complete normally.
[ needs fix ]
o all remaining, especially...
o Unnecessary semicolons
o Unnecessary casts from T to T
o The private field f is never read locally.
Issue Links
- relates to
-
GROOVY-833
Groovy-core compile errors in eclipse with 5.0 compiler enabled
-
Switching to 1.5 compiler yields 1700+ warnings and the 3 errors reported in http://jira.codehaus.org/browse/GROOVY-833 ... mainly complaining about type-safety. There's lurking another 2d+ work, when Groovy is "ported" to Java 5.