Bug 44435

Summary: [introduce parameter] should not do it for assignments
Product: [Eclipse Project] JDT Reporter: Dani Megert <daniel_megert>
Component: UIAssignee: Markus Keller <markus.kell.r>
Status: ASSIGNED --- QA Contact:
Severity: enhancement    
Priority: P3 CC: deepakazad
Version: 3.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Dani Megert CLA 2003-10-08 09:57:48 EDT 
I20031008

Having :
int i;
i= 3;

Introduce param for "i= 3"
==> compile error.

Introducing a param for an assignment doesn't seem to make that much sense even
though it is an expression that might result in a value.
Comment 1 Markus Keller CLA 2004-05-21 10:48:44 EDT 
moving target milestone
Comment 2 Markus Keller CLA 2004-06-09 07:09:12 EDT 
It doesn't lead to compile errors in general (e.g. when assignment is to a
field). We could consider raising a warning, but we should not block it if the
user wants to do it.

There are 2 issues:
(a) raise an error when extracting an expression containing local variables or
fields which are not accessible form all call sites.
(b) raise a warning when extracting an assigned expression.

Not for 3.0.