Bug 139719 - [change method signature] adapt default values when user changes type of new parameter
Summary: [change method signature] adapt default values when user changes type of new ...
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows 2000
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Markus Keller CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 299458 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-05-02 11:38 EDT by John Arthorne CLA
Modified: 2010-01-13 04:04 EST (History)
1 user (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 John Arthorne CLA 2006-05-02 11:38:40 EDT 
Build: 3.2 RC2

1) Checked out the project org.eclipse.equinox.common from eclipse.org
2) Select method "isUNC"
3) Refactor > Change Method Signature
4) Add a new boolean parameter to the method.
5) Finish.

The method Path.makeUNC() was updated by the refatoring with the following content:

		if (!(toUNC ^ isUNC(null)))
			return this;

I..e, it inserted the argment "null" to method isUNC, which results in a compile error.
Comment 1 Dani Megert CLA 2006-05-03 11:37:33 EDT 
User error ;-)
The dialog shows that 'null' is used as default value. Having said that, it should be smarter and use the default init value for the corresponding type.
Comment 2 Dani Megert CLA 2010-01-13 04:04:41 EST 
*** Bug 299458 has been marked as a duplicate of this bug. ***