On Jan 30, 9:16 pm, "Edward K. Ream" <[email protected]> wrote: > Renaming ivars, methods or classes is one of the most important kinds > of refactorings. > > I just realized that a relatively simple change will turn Leo's find/ > change commands into a rename command. The differences are: > > 1. Might be non-interactive. > > 2. Will check before making any changes in a node that the replacement > string does not already exist in the node. > > A *safe* find/replace would be a very important tool. For example, I > would like to make the types of lists more explicit by changing aList > to si_list, in those places where aList does, in fact, contain nothing > but ShortcutInfo nodes. > > Edward
While find/replace it is used to rename variables/class methods - it is not refactoring per se - it is just a string operation, a technical tool that is used to achieve a goal (this final goal being refactoring). Did you try rope for this? I've never used it for such big and complex codebases like leo, but for small pet projects (single source code file) it does the job. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
