Completely agreed. We'll most likely add the warning for this particular refactoring as a part of "safe refactoring" feature. Other refactorings also could be augmented with the warnings about possibly dangerous actions. Though this functionality is not the highest priority (at least in the context of Ariadna feature list).
Best regards, Eugene Zhuravlev JetBrains, Inc / IntelliJ Software, http://www.intellij.com/ "Develop with pleasure!" ----- Original Message ----- From: "Carlos Costa e Silva" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, April 15, 2002 18:58 Subject: RE: Re: [Eap-list] #616 Inline variable > > I think that it's definitely dangerous so a warning of some kind is > warranted. > > And after looking at all the possibilities, it's not so simple :( > > First, it's impossible to guarantee that the refactoring is completely > without side effects: > > Object a = x.abc(): > y.xyz(); > return a; > > y.xyz() may impact the return value of x.abc(). > > > So the only warning that should appear is if any of the variables used > in the initialization is reassigned: > > int a = x + y; > x = ...; // or y = ...; > return a; > > Any other warning would be way to intrusive. > > Carlos > > -- > Carlos Costa e Silva <[EMAIL PROTECTED]> > > > _______________________________________________ > Eap-list mailing list > [EMAIL PROTECTED] > http://www.intellij.com/mailman/listinfo/eap-list _______________________________________________ Eap-list mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-list
