Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 356689 - [move method] disables overloading and introduces behavioral change
Summary: [move method] disables overloading and introduces behavioral change
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.8   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-04 17:40 EDT by Gustavo Soares CLA
Modified: 2020-04-14 02:32 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gustavo Soares CLA 2011-09-04 17:40:00 EDT
Build Identifier: 20110615-0604

Moving a method may introduce a behavioral change by disabling an overloading 

Reproducible: Always

Steps to Reproduce:
1. Create the classes
public class A {
  public C c;
  public long k(int a) {
    return 2;
  }
  protected long k(long a) {
    return 1;
  }
}
public class B extends A {
  public long test() {
    return super.k(2);
  }
}
public class C {
}
2. Apply the move method refactoring to move k(int) to C.
public class A {
  public C c;
  protected long k(long a) {
    return 1;
  }
}
public class B extends A {
  public long test() {
    return super.k(2);
  }
}
public class C {
  public long k(int a) {
    return 2;
  }
}
3. The transformation changes behavior. After the transformation, the test() method returns 1 instead of 2
Comment 1 Eclipse Genie CLA 2020-04-14 02:32:33 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. 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.