Yes. In my case the CLASS macro declares several additional constructs that are required for this class to be used in a certain way. It can't be done otherwise.
*ah* I wondered if it was something like that. I just did not want to assume that was the reason.
Changing the code to read:
#ifndef VA_DOES_NOT_UNDERSTAND_THIS
#define CLASS(name) class name
CLASS(foo)
#else
class foo
#endif
{
public:
void bar();
};
fixes the problem, but it does make the code a bit harder to read, and it requires naming the class twice. Once for the real code, and once for the "dummy" class keyword that VA needs.
I have put in a bug report for VA not understanding this:
Refactoring menu stops working
Posted - Oct 26 2007 : 07:08:10 AM
