Bug 6956 - incorrect compiler error reported on extract method
Summary: incorrect compiler error reported on extract method
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.0 M2   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-12-14 12:44 EST by Adam Kiezun CLA
Modified: 2002-01-11 08:56 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 Adam Kiezun CLA 2001-12-14 12:44:21 EST
create 2 files:
A.java
class X { //note the name is different than cus name
}

B.java
class B extends X{
 void f(){
   /*[*/f();/*]*/
 }
}

try extracting the selected code - you'll see a message saying that X cannot be 
resolved. this problem is incorrectly reported and never shows up in the task 
list.

maybe the same old dance that you did with other problems like that would help 
here too?
Comment 1 Philipe Mulet CLA 2001-12-17 04:14:23 EST
Name resolution errors are always legite. Need to check what happened.
Comment 2 Philipe Mulet CLA 2001-12-19 06:25:19 EST
This is a standard error you get whenever attempting to resolve a secondary 
type name (X). If there was a reference to A before that, then X would be 
resolvable.

It will compile ok depending on the scenarii. A full build will pass A.java to 
the compiler upfront, thus X will be found. But an incremental compile might 
not find it.

Normal behavior. Won't fix.