Bugzilla – Full Text Bug Listing
| Summary: | [change method signature] removing parameter(s) gets rid of argument expressions | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Jongwook Kim <jongwook.kim> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | jongwook.kim |
| Version: | 4.5.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| 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. |
When the parameter (of type B) of method m is removed, m invocation does not evaluate the corresponding argument expression new B() after the refactoring. When the argument expression has side effects, the change-method-signature may change program behavior. BEFORE ----------------------------------- class A { void m(B b) {} void n() { new A().m(new B()); } } AFTER ----------------------------------- class A { void m() {} void n() { new A().m(); } }