Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
 All Forums
 Visual Assist
 Feature Requests
 Parsing Preprocessor Definitions?

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
yao_xuejun Posted - Apr 25 2006 : 9:18:12 PM
I notice that user defined preprocessor definitions can't be recognized by VAX, such as:

PreprocessorDefinitions="WIN32;_DEBUG;_CONSOLE;CYMT;HAVE_SAHASRA50000;TCAM_INGRESS;"

Code:

#ifdef TCAM_INGRESS
...
#endif

then the 'TCAM_INGRESS' isn't colord by VAX.

And, some predefined such as 'NDEBUG','_CONSOLE' is not colored.

It may be better if user have the choice to do it!

Thanks!
1   L A T E S T    R E P L I E S    (Newest First)
support Posted - Apr 26 2006 : 10:57:41 AM
Interesting suggestion. Simple examples might work. Setting PreprocessorDefinitions via anything but the simple assignment would certainly make it difficult to know what's defined at edit time.

Workaround is to #define all possible macros inside a #ifdef block that will never be compiled. VA X will see the definitions and recognize them as macros, but the code won't effect your run time.

#if 0
#define TCAM_INGRESS
...
#endif

If you don't want to touch your source with such an #if, add your #defines to stdafx.h in the Misc subdirectory of the VA X installation directory. Press Rebuild on the Performance node of our options dialog and restart your IDE.

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