Bugzilla – Full Text Bug Listing
| Summary: | [refactoring] Move Class changes behaviour in presence of overloading | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Friedrich Steimann <steimann> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | markus.kell.r, martinae |
| Version: | 3.3.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | stalebug | ||
Markus, can you comment? 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. If you have further information on the current state of the bug, please add it. 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. |
The semantics of the following trivial program is changed by moving either A or B to another package: package a; public class A { public void m(Object o) {System.out.println("o");} void m(String s) {System.out.println("s");} } package a; public class B { public static void main(String[] a) { (new A()).m("abc"); } } Is anyone working on visibility constraints (analogous to type constraints)? This could also answer the question whether visibility of m(Object) could be increased without changing behaviour. -- Friedrich