Summary: | ast: CompilationUnit::findDeclaringNode fails | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Adam Kiezun <akiezun> |
Component: | Core | Assignee: | Olivier Thomann <Olivier_Thomann> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 2.0 | ||
Target Milestone: | 2.0 M4 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Adam Kiezun
2002-03-19 10:26:32 EST
You are right. You should get the declaration of 'j' in the method declaration. I will fix it today. I hope you mean that you want the single variable declaration of 'j' in 'void m(int j){' and not the 'final int j = 0'. I am working on it. yes, argument j in declaration of void m(int j) My test case is: [ package test0311; public class Test { void m(){ final int j= 0; A a= new A(){ void m(int j){ int u= j; } }; } } ] and I don't get null when I ask for the declaring node of the binding I retrieve from the name 'j'. I don't have the right node, but I don't get null. Which version are you using? Oops, I had to change A in Test in the test case. Now I got null. The initial problem is fixed, but I need to find out why I could resolve bindings with a compiler error. *** Bug 11659 has been marked as a duplicate of this bug. *** Fixed and resolved in HEAD. |