Bugzilla – Full Text Bug Listing
| Summary: | [rename] Renaming Member Type in Superclass Leads to Undiagnosed Shadowing | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Max Schaefer <xiemaisi> |
| Component: | UI | Assignee: | Markus Keller <markus.kell.r> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | martinae |
| Version: | 3.3.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | stalebug | ||
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |
Build ID: M20071023-1652 Steps To Reproduce: Test case: class A { static class B { static int x = 42; } } public class D { static class C extends A { static int x = 23; static int m() { return C.x; } } public static void main(String[] args) { System.out.println(C.m()); } } This prints 23. Renaming the class A.B to C does not notice that the reference C.x in method C.m will now refer to A.C.x instead of D.C.x, so the resulting program prints 42. More information: