Summary: | [quick fix] rename on 'duplicate local variable' error should link more references | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Markus Keller <markus.kell.r> |
Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | ||
Version: | 3.2 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Markus Keller
2005-08-31 08:05:22 EDT
You can't always say that all the references to 'i' inside the copied block really refer to the inner i. It could be wrong and then this extra feature would hurt you. I also think that the AST bindings always go to the outer i. So it's not a trivial reuse of local rename (Have to check that) > You can't always say that all the references to 'i' inside the copied block > really refer to the inner i. Agree > It could be wrong and then this extra feature would hurt you. Disagree. Currently, only the second declaration is linked, which is equivalent to just changing the name without using a quick fix. You would not lose any functionality if my proposal was implemented. > I also think that the AST bindings always go to the outer i. So it's not a > trivial reuse of local rename (Have to check that) Yes, there's no binding for the seconf declaration, and all references bind to the first declaration. |