Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
User name:
Password:
Save Password
Forgot your password?

 All Forums
 Visual Assist
 Technical Support
 "List Functions in File" parsing question
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

MikeBeard
New Member

USA
3 Posts

Posted - Feb 01 2008 :  11:44:18 AM  Show Profile  Reply with Quote
I ran across some code that makes the list functions not work correctly. Is this a known problem and/or is there a work around for it?

There seems to be some odd interaction with #if 0 and operator=. It's confusing, but I run across it a bunch in my code-base.

I'll paste the code below this. It's not long.

Thanks,
Mike

=============================

// VA_X.dll file version 10.3.1561.0  built 2007.09.13
//
// the "List Methods in File" dropdown does NOT show the following 
// function as it is right now.
//
// To make it show up, do one of the following:
//   - comment out the #if (or remove that line)
//   - change the '0' to something like FRED
//   - just remove the '0' (won't compile, but it will 
//     see the function)
//   - remove the '=' from the ::operator=(), to make it 
//     just the operator()
//    
// There might be others, but I can't think of anything else to try

#if 0
SomeClass& SomeClass::operator=(const MyClass & rX)
{
    return *this;
}
#endif

feline
Whole Tomato Software

United Kingdom
18943 Posts

Posted - Feb 01 2008 :  12:42:56 PM  Show Profile  Reply with Quote
I am seeing the same effect here. Thank you for the clear description.

case=12168

For me, using VA 1626, the function is shown in VA Outline, which is something.

zen is the art of being at one with the two'ness
Go to Top of Page

MikeBeard
New Member

USA
3 Posts

Posted - Feb 01 2008 :  3:10:27 PM  Show Profile  Reply with Quote
No problem.

I had been seeing this on and off for awhile and finally had 30 minutes to kill and decided to figure out what (if I could) seemed to be causing it. This seemed to match the pattern in the code I help maintain.

Yeah, I need to upgrade again to be able to get the later builds. Hopefully I'll do that soon.

Mike
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
18943 Posts

Posted - Feb 01 2008 :  3:13:44 PM  Show Profile  Reply with Quote
For now you could simply run a find and replace, to replace #if 0 with #ifdef IGNORE_THIS_CODE

A little more wordy, but it would fix the problem

zen is the art of being at one with the two'ness
Go to Top of Page

MikeBeard
New Member

USA
3 Posts

Posted - Feb 01 2008 :  3:16:37 PM  Show Profile  Reply with Quote
Yes, I will probably do that. Though in most cases, I'll probably just remove the code. Don't know why it was left in. That's what version control is for!
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000