| Author |
 Topic  |
|
|
Uniwares
Tomato Guru
Portugal
2321 Posts |
 Posted - May 19 2004 : 9:50:41 PM
|
| VS6 - Naming a variable in causes VAX to color the variable as keyword. "in" is not a valid keyword in C++, so it should be recognized as variable. |
|
|
LarryLeonard
Tomato Guru
USA
1041 Posts |
Posted - May 20 2004 : 03:14:05 AM
|
| Without looking, I recall there's a #define somewhere of "IN" as nothingness; it's used in ATL, I think, just as a way to mark function parameters. Could that be the culprit? |
 |
|
|
support
Whole Tomato Software
5566 Posts |
Posted - May 20 2004 : 09:45:26 AM
|
| We suspect Larry is correct. We can reproduce the problem if we define "in" in another header. |
Whole Tomato Software, Inc. |
|
|
|
Uniwares
Tomato Guru
Portugal
2321 Posts |
Posted - May 20 2004 : 09:54:50 AM
|
| "in" is not defined, you'll see it also in the HCB right between "interface", "int" and "inline" |
|
|
|
Uniwares
Tomato Guru
Portugal
2321 Posts |
Posted - May 25 2004 : 01:34:47 AM
|
Sorry guys, but this version has serious association problems.
I see lots of variables colored as functions, enums or keywords. Typical errors are "size", "begin" and "end", all of which are STL functions, when I define a variable of this name, it will be colored as symbol in the source window. Strangely the definition bar shows it in all blue.
I have one enum named "data", all variables named data are colored as enums. This did definitely not happen with previous builds. |
|
|
|
WannabeeDeveloper
Tomato Guru
Germany
775 Posts |
Posted - May 25 2004 : 02:10:16 AM
|
Same here, since Build 1235...
and already classified by WT as case=82... |
 |
Edited by - WannabeeDeveloper on May 25 2004 03:14:05 AM |
|
|
| |
Topic |
|
Topic Locked
