Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
 All Forums
 Visual Assist
 Technical Support
 1548: Another Move Implementation

You must be registered to post a reply.
Click here to register.

Screensize:
UserName:
Password:
Format: BoldItalicizeUnderlineStrikethrough Align leftCenterAlign right Insert horizontal ruleUpload and insert imageInsert hyperlinkInsert email addressInsert codeInsert quoted textInsert listInsert Emoji
   
Message:

Forum code is on.
Html is off.

 
Check to subscribe to this topic.
   

T O P I C    R E V I E W
diavo Posted - Mar 09 2007 : 02:40:04 AM
A little unimportant error:

class test
{
test(int i) {int j;};
}


results after move implementation in


class test
{
test(int i);;
}



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.
2   L A T E S T    R E P L I E S    (Newest First)
sean Posted - Mar 09 2007 : 11:14:23 AM
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.
feline Posted - Mar 09 2007 : 11:03:22 AM
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:

http://docs.wholetomato.com?W382

© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000