| T O P I C R E V I E W |
| swinefeaster |
Posted - Dec 08 2008 : 8:02:38 PM
*shudder*
i hate to ask this, but the code i am working on now uses code such as:
#define GAMECOMMON_NAMESPACE_BEGIN \ namespace Common { namespace GameCommon {
#define GAMECOMMON_NAMESPACE_END } }
to define namespaces, and VAX can't handle this. i know it's a really stupid way to do things, but i'm not sure if i can get them to change it as it's (ab)used in a lot of places.
any way vax would be able to parse these macros? does it parse any macros currently?
thanks
swine |
| 3 L A T E S T R E P L I E S (Newest First) |
| sean |
Posted - Dec 09 2008 : 3:16:09 PM
set VANet8 if you are using vs2005 or VANet9 if you are using vs2008.
Also delete the proj_* directories from the VA db dirs to force a reparse of the projects.
|
| swinefeaster |
Posted - Dec 09 2008 : 2:50:05 PM
I'm only using C++, do I still need to set the VANet8 one? I set the Visual Assist X but it had no effect. |
| sean |
Posted - Dec 09 2008 : 01:41:52 AM
You aren't the first unfortunately (case=11759). You may have some improvement by setting the following reg entries (replace VANet8 with VANet9 for vs2008). However, these setting do have side effects at the current time - for example, some members of std::string go missing with these values.
REGEDIT4
[HKEY_CURRENT_USER\\Software\\Whole Tomato\\Visual Assist X]
"LimitMacro"="No"
[HKEY_CURRENT_USER\\Software\\Whole Tomato\\Visual Assist X\\VANet8]
"LimitMacroParsing"=hex:00
|
