Bug 8697 - 2 compiler bugs: the operator unkown operator is undefined and defined in an inherited type and an enclosing scope
Summary: 2 compiler bugs: the operator unkown operator is undefined and defined in an...
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P1 normal (vote)
Target Milestone: 2.0 M3   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 8706 8709 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-01-29 14:38 EST by Johan Compagner CLA
Modified: 2002-01-31 05:41 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Johan Compagner CLA 2002-01-29 14:38:57 EST
am trying to recompile the JDK1.4 classes so that i can really de bug through 
them
and i can't comple the com.sun.imageio.plugins.jpeg.JFIFMarkerSegment

the error is:

The field thumbWidth (and height) is defined in an inherited type and an 
enclosing scope.

and this method gives me an compilere error:

public Frame cancel()
 {
  Frame sharedOwnerFrame = null;
     if (sharedOwnerFrame == null) {
         sharedOwnerFrame = new Frame() {
             public synchronized void dispose() {
             }
         };
     }
     return sharedOwnerFrame;
 }

the error:
the operator unkown operator is undefined for the argumetns type(s) 
java.awt.Frame, <anonymous subclass of Frame>

this is a piece of code of SwingUtilities.
Comment 1 Philipe Mulet CLA 2002-01-29 18:19:56 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.
Comment 2 Philipe Mulet CLA 2002-01-29 18:43:45 EST
*** Bug 8709 has been marked as a duplicate of this bug. ***
Comment 3 Olivier Thomann CLA 2002-01-30 10:03:33 EST
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.
Comment 4 Olivier Thomann CLA 2002-01-30 10:16:09 EST
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.
Comment 5 Olivier Thomann CLA 2002-01-30 10:45:30 EST
I found a fix. I will release it as soon as I entered regression tests for this 
PR.
Comment 6 Olivier Thomann CLA 2002-01-30 12:20:04 EST
Released in HEAD.
Comment 7 Philipe Mulet CLA 2002-01-31 05:41:22 EST
*** Bug 8706 has been marked as a duplicate of this bug. ***