| Summary: | [pull up] Pull Up a field enables field hiding | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Melina Mongiovi <melmongiovi> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | manju656 |
| Version: | 4.3 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
As mentioned in bug 234980, program semantics is changed after the pull up refactoring. *** This bug has been marked as a duplicate of bug 234980 *** |
Program's behavior changes after pulling up a field. Reproducible: Always Steps to Reproduce: 1. Create the classes package p1; public class A { protected int f = 10; } package p1; public class B extends A { public long m() { return f; } } package p1; public class C extends B { private int f = 11; } 2. Apply the pull up field refactoring (pll up the field f from C to B) package p1; public class A { protected int f = 10; } package p1; public class B extends A { private int f = 11; public long m() { return f; } } package p1; public class C extends B { } 3. After the transformation, the ”m” method returns 11 instead of 10.