Bug 5413 - incorrect class source range
Summary: incorrect class source range
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P5 normal (vote)
Target Milestone: 2.0 M2   Edit
Assignee: Olivier Thomann CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-01 08:11 EST by Adam Kiezun CLA
Modified: 2002-01-14 11:50 EST (History)
0 users

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-11-01 08:11:59 EST
package junit.framework;
public class A {
	void t(){}
}
class B extends A{
	public void f(){
	}
	public void second(int y){}
	public void s(){}
	public void sd(){}
}
//class C extends A{
//	void f(){}
//}
//class E extends A{
//	private void f(){}
//	public void second(){}
//}
//class F extends A{
//	protected void f(){
//	}
//}
class G extends A{
	public int sd(){return 0;}
}

source range for G includes 1 line of comment from another class
Comment 1 Olivier Thomann CLA 2001-11-28 11:03:23 EST
The fix is located in the checkAnnotion() method of the Parser. But fixing this 
problem breaks a lot of in the JDOM code and the JDOM tests. JDOM includes the 
comment preceeding a member even if this comment is not a javadoc comment.
So we cannot break this code right now and we have to defer this PR till the 
actual JDOM implementation is replaced with the new DOM nodes.
Comment 2 Olivier Thomann CLA 2001-12-13 12:30:29 EST
Fix released in HEAD. Change in the Parse::checkAnnotation()