AND a second question: is there any way to avoid jumping to the implementaion file after using that refactoring. This is very annoying if I have to refactor a lot of functiion like that: I always have to switch back to the header file to get the next one.
I am seeing the same effect here. Thank you for the clear description.
case=5432
As for jumping to the cpp file, we try to avoid to much file changing during the refactoring operations. One good solution would be to use a macro to call Move Implementation to Source File, and then call alt-o afterwards. See here for the details on how to use macro's with VA's refactoring:
The pre-existing semi-colon is not part of the implementation so is not considered when the implementation is turned into a declaration. That is, the semi-colon after } is spurious and ignored.
1548: Another Move Implementation
Posted - Mar 09 2007 : 02:40:04 AM
