I declare an enum similar to this: typedef enum {a,b,c} MYTYPE; The type is inside a C++ namespace. The namespace name is controlled with a #define: #define PROJECT_NAMESPACE MyNamespace In several source files I have the following: using PROJECT_NAMESPACE::MYTYPE; If I rename MYTYPE using VAX then all the 'using' statements are missed. Dimitris
The problem with quick & dirty is that the dirty remains long after the quick has been forgotten.
Sorry, I didn't provide adequate description. What I described happens when I have an enum with a type specification:
VAX seems to be having a little trouble with the type specification. If I enter a using statement for the whole namespace, then VAX considers the enum type name invalid and underlines it:
If I enter "using PROJECT_NAMESPACE::MYTYPE;" the VAX treats the type name as legal and does not underline it (as in the first picture).
My problem is not just aesthetic. I use a very central enum of unsigned __int64 because I don't want to use #defines and right now VAX forces me to write a using MYNAMESPACE::MYTYPE on every source file, otherwise I get a screen full of red underlines.
Warm Regards Dimitris Staikos
The problem with quick & dirty is that the dirty remains long after the quick has been forgotten.
Renaming a type misses 'using' declarations
Posted - Nov 25 2010 : 01:29:05 AM
