Bug 56948 - Extract local variable does not do the right thing for "new Object()" [refactoring]
Summary: Extract local variable does not do the right thing for "new Object()" [refact...
Status: RESOLVED DUPLICATE of bug 27740
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P4 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-31 13:56 EST by Oyvind Harboe CLA
Modified: 2006-03-22 05:11 EST (History)
0 users

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 Oyvind Harboe CLA 2004-03-31 13:56:51 EST 
Example:

				Object a=new Object();
				Object b=new Object();

=>
				Object object = new Object();
				Object a=object;
				Object b=object;
Comment 1 Dirk Baeumer CLA 2004-04-01 02:42:55 EST 
Extract local doesn't have any logic to check if the extraction causes side 
effects. There is a check box on the dialog letting you control whether all 
occurrences should be replaced.

Not critical for 3.0.
Comment 2 Markus Keller CLA 2006-03-22 05:11:38 EST 

*** This bug has been marked as a duplicate of 27740 ***