Bugzilla – Full Text Bug Listing
| Summary: | Rename instance variable refactoring could be smarter[refactoring] | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Erich Gamma <erich_gamma> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | CC: | akiezun |
| Version: | 2.0 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
not 2.0 reopeing to move to inbox no action planned without external contribution bugzilla! As said, no action planned without external help As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you. |
consider public class A { int foo; void m(int bla) { foo= 1; } rename the instance variable from foo -> bla we properly warn the user, but we could avoid the ambiguity by inserting "this": void m(int bla) { this.foo= 1; } These cases are rare in particular when using the fPrefix convention, but it would be smart.