Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
 All Forums
 Visual Assist
 Technical Support
 VA1444: Macro parameter limitation?

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
squidge Posted - Mar 22 2006 : 04:38:04 AM
I was wondering if VA had any built in macro parameter limitations? Just as I see that when using certain things like the TRACE macro with more than 9 arguments, VA doesn't parse the code following the macro correctly, and underlines all variables with red wavy underlines.

I've managed to reproduce this with the following snippet of code as an example:

6   L A T E S T    R E P L I E S    (Newest First)
squidge Posted - Mar 28 2006 : 07:33:02 AM
I've rebuild the symbol database and restarted the ide, and the same problem occurs.

Since it doesn't occur for you with the exact code in the picture, I'll try to create a standalone project and see exactly what causes it.
jpizzi Posted - Mar 26 2006 : 8:41:27 PM
Well, I have tried this with VS 2005 and VA 1444, too.

The variables following (using your exact code) are properly parsed. Now, we need to look into what the differences are between your project and installation and mine, to see if we can find the problem.

First question: Does Clearing the history and rebuilding the symbol database help (VA Options, Performance, General)?
squidge Posted - Mar 26 2006 : 05:15:26 AM
VA_X.dll file version 10.2.1444.0 built 2006.03.12

Visual Studio 2005.


jpizzi Posted - Mar 23 2006 : 10:05:21 PM
OK. Using VS .NET 2003 and VA 1444, it works as expected. What version of the IDE and VA are you using? I'll try that one, to see if there is something else affecting this.
squidge Posted - Mar 23 2006 : 5:51:54 PM
"TRACE" is defined as follows:

#define ATLTRACE ATL::CTraceFileAndLineInfo(__FILE__, __LINE__)
#define TRACE ATLTRACE

class CTraceFileAndLineInfo
{
CTraceFileAndLineInfo(const char *pszFileName, int nLineNo)
(...snip...)
void __cdecl operator()(const char *pszFmt, ...) const
(...snip...)

So, as you can see, The version of TRACE I am using can take a variable number of arguments.

Strange thing is, VA seems to be perfectly happy with upto 9 arguments. Go over this limit though, and you get the effect as shown in the picture.
jpizzi Posted - Mar 23 2006 : 12:27:10 AM
I notice that TRACE is a macro defined in VA's stdafx.h with only one parameter. Perhaps this is confusing things? Where does the TRACE you expect to use come from? I could not find one that looked like it would take 9 parameters.

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