[GROOVY-834] Many, many compiler warnings (Eclipse 3.1 M6)

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0-JSR-1
• Fix Version/s: 1.0-JSR-4
• Environment: Eclipse 3.1M6, using 1.4 compiler settings and enabled many warnings
• Assignee: sormuras
• Reporter: sormuras
• Created: 05/May/05 00:05
• Updated: 30/Nov/07 06:23
• Resolved: 15/Nov/05 03:50

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