Bug 234981 - [push down] method changes program semantics in presence of overloading
Summary: [push down] method changes program semantics in presence of overloading
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
: 292981 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-05-31 06:37 EDT by Friedrich Steimann CLA
Modified: 2022-05-16 17:15 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Friedrich Steimann CLA 2008-05-31 06:37:59 EDT 
Build ID: I20080523-0100

Steps To Reproduce:

class A {
  void m(Object o) {…}
  void m(String s) {…}
  void n() {m("a");}
}
class B extends A {
}

Pushing down m(String) from A to B changes binding of call in A.

More information:

converse of http://bugs.eclipse.org/234980

Again, silent change of program semantics not acceptable for a refactoring.
Comment 1 Dani Megert CLA 2009-10-22 03:17:52 EDT 
*** Bug 292981 has been marked as a duplicate of this bug. ***
Comment 2 Eclipse Genie CLA 2020-05-22 19:21:04 EDT 
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.
Comment 3 Eclipse Genie CLA 2022-05-16 17:15:09 EDT 
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.