Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
 All Forums
 Visual Assist
 Technical Support
 #define resolution error in build 1438

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
gunvulture Posted - Dec 22 2005 : 2:16:28 PM
This is not new to 1438.

I have stuff like:
#define g_Time Time::GetSingletonRef(0)

and VAX isn't parsing the type correctly. This is under VS 2k5. If I type
"g_Time." in code, Nothing shows up. "g_Time.GetSomething(" displays "#define g_Time Time::GetSingletonRef(0)..." in a tooltip, whether or not GetSomething() is a valid function in class Time.

I have the the "evaluate all macros used in definitions" option enabled.

1   L A T E S T    R E P L I E S    (Newest First)
support Posted - Dec 22 2005 : 10:29:22 PM
You won't get what you want. VA X doesn't evaluate as you reference symbols, only when you define them. Since you aren't using g_Time in a definition, VA X won't look at what VA X is when you reference it.

You get a tooltip explaining what g_Time is when you use it. VA X isn't checking that you use it correctly. (We omit the lengthy debate over the merit of #define, and why C# doesn't have it, but your example is a plug for proponents of C#.)

Also... We recommend you disable "evaluate all macros..." and rebuild your symbol database. The option is useful only in rare cases (and your not using g_Time in a definition anyhow.)

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