Summary: | 2 compiler bugs: the operator unkown operator is undefined and defined in an inherited type and an enclosing scope | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Johan Compagner <jcompagner> |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P1 | CC: | Olivier_Thomann |
Version: | 2.0 | ||
Target Milestone: | 2.0 M3 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Johan Compagner
2002-01-29 14:38:57 EST
The first error is legite, since you need to toggle the Eclipse compiler in 1.4 mode (not yet doable in UI) to get this behavior. From 1.4 on, inherited members prevail on enclosing ones. In the meantime, you can qualify the offending code with 'this.'. The other 2 errors are more curious, will investigate and keep you posted. *** Bug 8709 has been marked as a duplicate of this bug. *** The second bug is due to a wrong operator. A compound assignement is created for the '=' operator instead of an Assignment. One int is not popped properly from the int stack in the parser. I am investigating this case. The first problem is due to an extra int pushed on the int stack because of the synchronized modifier. I am investigating now how to get rid of it. I found a fix. I will release it as soon as I entered regression tests for this PR. Released in HEAD. |