Bugzilla – Full Text Bug Listing
| Summary: | Missing binding on non-visible type | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Martin Aeschlimann <martinae> |
| Component: | Core | Assignee: | Kent Johnson <kent_johnson> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | minor | ||
| Priority: | P3 | ||
| Version: | 3.1 | ||
| Target Milestone: | 3.1 M4 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
I will investigate. Kent, in this case we don't return any binding for the new XX(). Can this be easily changed? The resolvedType of the SingleTypeRef (new XX()) now remembers the invisible member type. Verified in 200412140800 |
20041007 In the following scenario, XX is not visible (as private). The compiler marks this at 2 locations in the qualified name and in the constructor invocation. Use the AST view to look at the bindings: - The second reference to 'XX' has no binding, the first has one It would be nice if the second reference also could have the binding. Quick fix uses these bindings to offer to correct the visibility. package a; public class G { public void useX() { X x= new X(); X.XX l= x.new XX(); } } package a; public class X { private class XX { } }