Whole Tomato Software Forums

Whole Tomato Software Forums

All Forums

Visual Assist

Technical Support

broken find-references (v.1819)

You must be registered to post a reply.
Click here to register.

Screensize:

UserName:

Password:

Format:

Message:

Forum code is on.
Html is off.

Check to include your profile signature.
Check to subscribe to this topic.

T O P I C R E V I E W
Michal Puczynski	Posted - Apr 14 2010 : 06:00:52 AM The following code causes VA parser to fail. #if _MSC_VER < 1300 if (ERROR_SUCCESS==RegKey.QueryValue(RegParams,_T("Parameters"),&dwLen)) #else if (ERROR_SUCCESS==RegKey.QueryStringValue(_T("Parameters"),RegParams,&dwLen)) #endif { bIgnoreServiceParam = true; lpParsedParams = RegParams; } The lines are within a method. The parser is unable to find the end of the method and thinks it follows to the end of source file. When I try find-references to symbols within the code, VA find result reports all references being a part of the function. Following functions are not reported at all. When #if _MSC_VER < 1300 .. #else .. #endif is removed VA works fine. VA 1819, in VC++ 2003 SP2, no other plugins, intellisense disabled in registry.
7 L A T E S T R E P L I E S (Newest First)
feline	Posted - Apr 27 2010 : 3:25:06 PM Appologies for the delay in getting back to you about this. I have tested the following code in VS2003 with VA 1814, 1819 and 1822: void testFelineFuncBeforeTestCode() { } void testFelineFuncHoldingTestCode() { bool bIgnoreServiceParam; void *lpParsedParams; #if _MSC_VER < 1300 if (ERROR_SUCCESS==RegKey.QueryValue(RegParams,_T("Parameters"),&dwLen)) #else if (ERROR_SUCCESS==RegKey.QueryStringValue(_T("Parameters"),RegParams,&dwLen)) #endif { bIgnoreServiceParam = true; lpParsedParams = RegParams; } } void testFelineFuncAfterTestCode() { bool bIgnoreServiceParam; bIgnoreServiceParam = false; } when I do a Find References search for "bIgnoreServiceParam" in either function, VA only returns the references inside that function. Can you try this test on your system please? It is possible you will see a different result, and if you do, I am wondering if the problem is file or solution specific.
Michal Puczynski	Posted - Apr 21 2010 : 02:44:13 AM I did that before reverting to 1814 with no result.
accord	Posted - Apr 20 2010 : 3:36:52 PM Are you aware of that the underlines appear only in modified files? This behavior can seem erratic if you don't aware of that. Installing builds may trigger rebuild symbol databases so it may caused the difference. In this case VA1819 would work now. You can trigger this manually via VA Options -> Performance -> Rebuild symbol databases Worth trying this when things go wild. But normally you don't have to use or even know about this option.
Michal Puczynski	Posted - Apr 20 2010 : 10:26:42 AM I was worth trying older build. I rolled back to 1814 and this one is able to recognize the #if stuff correctly together with following code. I decided to dig deeper as I had numerous other problems with #if and #ifdef clauses. ex. when writing number of code changes under #ifdef/#else/#endif parser was unable to recognize variable definitions. In large parts of code those variables were underlined red. After reinstalling 1814 instead of 1819 all gets back to normal.
accord	Posted - Apr 15 2010 : 03:50:42 AM I see. The problem is that I didn't see the problem that you are seeing even with your original code (when nothing was commented out) I asked you to check the behavior in a new project to draw conclusions. Another possibility is to send the whole file or at least the whole function to us to see if this helps. It is not normally possible, but worth mentioning. You can send the files via the form: http://www.wholetomato.com/support/contact.asp if you decide to do it. Please include the URL of this topic in the description so we can match it up. It is important for us to be able to reproduce the problem on our side to be able to fix it.
Michal Puczynski	Posted - Apr 15 2010 : 03:26:05 AM I doubt it. It is a very simple test. I comment the #if part and it works, when I revert to original it is back wrong.
accord	Posted - Apr 14 2010 : 4:55:00 PM I wasn't able to reproduce this. Can you please try if you can reproduce this in a clean new win32 project? I'm wondering if something in your project or in the surrounding code causes this.

Snitz Forums 2000