| T O P I C R E V I E W |
| kmw |
Posted - Sep 16 2008 : 9:33:50 PM
I've read some other problems related to VA X and boost::bind. We're evaluating VA X for a possible purchase for our group. We're heavy users of boost and of boost::bind, so having this not work could be a deal breaker. The main problem is that the symbol is underlined as an unknown symbol and so is not highlighted properly in addition. The rest of boost that I've sampled in our source code seems to display correctly in VA X. Having to put sprinkle workarounds of defining "namespace boost { void bind ( ... ); }" in our code may not fly as a solution. Is there an update on this issue, will this be fixed?
system info:
VA_X.dll file version 10.4.1647.0 built 2008.07.30
DevEnv.exe version 8.0.50727.762
msenv.dll version 8.0.50727.762
Font: Courier New 13(Pixels)
Comctl32.dll version 6.0.2900.2982
Windows XP 5.1 Build 2600 Service Pack 2
Single processor
Platform: Custom
Stable Includes:
c:\\Program Files\\Microsoft Visual Studio 8\\VC\\include;
c:\\Program Files\\Microsoft Visual Studio 8\\VC\\atlmfc\\include;
c:\\Program Files\\Microsoft Visual Studio 8\\VC\\PlatformSDK\\include;
c:\\Program Files\\Microsoft Visual Studio 8\\SDK\\v2.0\\include;
C:\\p4.2\\hw\\tools\\boost\\boost-1.33.0;
C:\\p4.2\\hw\\tools\\wxWidgets-2.8.8\\include;
Other Includes:
Stable Source Directories:
c:\\Program Files\\Microsoft Visual Studio 8\\VC\\atlmfc\\src\\mfc;
c:\\Program Files\\Microsoft Visual Studio 8\\VC\\atlmfc\\src\\mfcm;
c:\\Program Files\\Microsoft Visual Studio 8\\VC\\atlmfc\\src\\atl;
c:\\Program Files\\Microsoft Visual Studio 8\\VC\\crt\\src;
|
| 6 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Oct 02 2009 : 08:57:38 AM
Unfortunately this is still an outstanding bug, so for now the stdafx.h modification is the way to go. This thread should be updated when the problem is fixed.
Some of the boost library code is quite complex to parse, and it is causing us some problems, as you can see. |
| GKarRacer |
Posted - Oct 01 2009 : 4:17:37 PM
Has this ever been fixed? Or is the stdafx.h modification still the way to go? I still see this phenomenon. |
| kmw |
Posted - Sep 17 2008 : 7:17:20 PM
Yes, that seems to have worked. I had to add an entry for boost::function0 as well. |
| feline |
Posted - Sep 17 2008 : 6:50:10 PM
I think I have now replied to your other threads. I have just replied to the std::vector thread 
Does modifying VA's StdAfx.h file help with the boost::bind underlining? |
| kmw |
Posted - Sep 17 2008 : 4:37:48 PM
> Are you seeing other problems as well as boost::bind ?
Thanks for the reply.
I have two other messages on the forums. In one of our projects it seems the STL (from VC default libraries) is not being parsed correctly, or something in the project is preventing it from being parsed correctly (e.g., with "std::vector", "vector" is highlighted as a method instead of as a stable included class. In small toy projects it seems to work fine. |
| feline |
Posted - Sep 17 2008 : 3:27:52 PM
Unfortunately boost::bind being underlined as a mistyped symbol is a known problem and is on our list of things to fix:
case=9325
If you turn on:
VA Options -> Advanced -> Listboxes -> Get content from default Intellisense
this should help with listboxes. Generally VA should work correctly with both Boost and wxWidgets.
If you find that namespace boost { void bind ( ... ); } helps then try adding this to VA's StdAfx.h file as explained in this FAQ entry:
http://docs.wholetomato.com?W302
at the bottom. This file is used to help VA's parser with difficult code, and can be used to work around odd effects. After modifying this file you need to rebuild the VA symbol database for the changes to take effect:
VA Options -> Performance -> General -> Rebuild symbol databases
This way you only need to make the change once, in one place, and it does not impact your actual solution code.
Are you seeing other problems as well as boost::bind ? |
