On 7/15/05, JeDi <jeroen.dierckx@gmail.com> wrote:

> 
> And about code refactoring: it would be a _very_ cool feature, but it
> can only be used if it would _always_ be correct. If you rename a
> method for example, it's of no use if you'll have to check all the
> modified source files afterwards. Some sort of log, where you can see
> what has been changed by the refactoring, is certainly needed I guess.

When refactoring, eclipse displays a window where you can check what
will be changed. You can select files/classes that are going to be
modified in a tree, and the changes are displayed using the difference
viewer.

By the way, for a java app, eclipse is pretty fast when it comes to
code completion and on-the-fly parsing, and has implemented a lot of
useful refactoring operations, so it might be a worthwhile source of
inspiration, especialy as it's open-source, unlike visual assist -
even tough it's java and not C++.

_______________________________________________
KDevelop-devel mailing list
KDevelop-devel@barney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel