| T O P I C R E V I E W |
| timepp |
Posted - Jul 25 2006 : 10:44:17 PM
VA_X.dll file version 10.2.1445.0 built 2006.04.12
VAOpsWin.dll version 1.3.2.4
VATE.dll version 1.0.4.15
DevEnv.exe version 8.0.50727.42
msenv.dll version 8.0.50727.42
Font: Courier New 12(Pixels)
Comctl32.dll version 6.0.3790.1830
WindowsNT 5.2 Build 3790 Service Pack 1
Single processor
Platform: Win32
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;
Library Includes:
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;
Other Includes:
-----------------------------------------------------------
Windows 2003 SP1
VS2005
windows console project without precompiled header support
|
| 3 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Jul 29 2006 : 12:13:00 PM
this is certainly possible. plus, some builds of VA pick up single letter variable names as being the same as symbols from the stable include directories.
in both cases, using slightly longer, more unique variables names should fix the problem. if it does not then we have a different issue. |
| bugfix |
Posted - Jul 27 2006 : 11:47:38 AM
I think it's the problem w/ 14xx builds and .net 2.0 framework.
http://forum.wholetomato.com/forum/topic.asp?TOPIC_ID=4249 |
| feline |
Posted - Jul 26 2006 : 7:45:03 PM
that is odd. if you try the latest beta, 1530, do you still get this? i am not seeing this problem with VS2005 and VA 1530 in C++.
the other thing to try is longer names for the structure and variables. this helps the colouring code to know what is going on, and is easier to make sense of later on  |
