I didn't think of using introduce parameters that way, but I see that it could be useful.
But I would really like an intelligent change signature refactoring - add the parameter to a method call and have an intention to change the method signature. Idea has made me used to not having to use wizards (where code-completion is not available for example) to do things like change signature. Carlos "Mike Aizatsky" <[EMAIL PROTECTED]> wrote in message adirre$97j$[EMAIL PROTECTED]">news:adirre$97j$[EMAIL PROTECTED]... > Carlos, > > The problem is that this refactoring is not targeted at situations you've > described. We use it when you are passing some parameters to a method and > perform some computation with parameters, which can (and should) be easily > be performed at the call site (e.g. eliminating ex-this variable after "make > state" refactoring to pass only needed fields, making code less dependant of > other subsystems, etc.) So it's purpose is not "change signature" as you > describe, but intelligent parameter creation by calculating it at each call > site. > > -- > Best regards, > Mike Aizatsky. _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
