Summary: | [1.5][enum] erroneous strictfp keyword on enum type produces error on constructor | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Tom Hofmann <eclipse> | ||||
Component: | Core | Assignee: | Olivier Thomann <Olivier_Thomann> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | minor | ||||||
Priority: | P3 | CC: | philippe_mulet | ||||
Version: | 3.1 | ||||||
Target Milestone: | 3.1 M6 | ||||||
Hardware: | PC | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Tom Hofmann
2005-02-16 08:20:27 EST
strictfp seems to be allowed on Enum types. The second case should not report a problem. Created attachment 17988 [details]
Apply on HEAD
This is fixing the second error.
strictfp is allowed as an enum type modifier, but it is not allowed as a constructor modifier. If the enum type is set as strictfp, the constructor binding is also set as strictfp as well as the enum synthetic methods (valueOf and values). Philippe, I will add this support in the binding of these synthetic methods. So the only modifier that can be set in the source for an enum constructor is private. Fixed and released in HEAD. Regression test added in EnumTest.test079 Verified in 20050330-0500 |