|
accord
Whole Tomato Software
United Kingdom
3287 Posts |
 Posted - May 15 2007 : 12:47:35 PM
|
Can be used VA Outline's information to achieve a better "create implementation", "create declaration" and "move implementation to source"?
Now this 3 refactorings are grouping class functions and overloads together.
But using VA Outline's rich informations available, you can create an even better implementation to these refactorings.
Yes, the already discussed ordering.  Yes, I can use the new outline feature, but when I working with medium or large files, it is faster to refactor manually (copy-paste) then using create implementation, than finding the function the right place in outline and then drag the function.
What I think is the following:
When I use create implementation, VAX can see the prev. and the next function name in the header. Then VAX can search for this 2 function name in the cpp, and put the implementation between those functions. If cannot find those functions then the default (current) behavior can be applied. (Certainly if the function was the first or last in the class, then it should be the first/the last in the cpp also.)
The same applies to "create declaration" and "move implementation to source"
So what I am talking about is a better default placing of functions. |
Edited by - accord on May 15 2007 1:12:42 PM |
|
|
feline
Whole Tomato Software
United Kingdom
19021 Posts |
Posted - May 16 2007 : 08:13:40 AM
|
Unfortunately VA Outline is something of a red herring at this point. What you say makes a lot of sense *but* this assumes the ordering of functions in the cpp file is something like the ordering in the header file.
If they happen to be similar then this works, but there is still a problem that VA does not properly distinguish overloaded functions, which confuses the situation.
We are looking into improvements in this area. |
zen is the art of being at one with the two'ness |
 |
|
VA Outline and create implementation
