| T O P I C R E V I E W |
| cgough |
Posted - Aug 27 2007 : 11:25:15 AM
I think the typedef thing has been discussed in other topics but not quite like this.
class T
{
public:
protected:
private:
typedef struct X
{
int m_y;
int m_z;
}m_C;
struct Y
{
int y;
int z;
}m_Y;
};
m_C does not match the color of m_Y
Thanks
Chris
VA_X.dll file version 10.3.1559.0 built 2007.07.06
VAOpsWin.dll version 1.3.2.4
VATE.dll version 1.0.5.8
DevEnv.exe version 7.10.3077.0
msenv.dll version 7.10.3077.0
Font: Bitstream Vera Sans Mono 11(Pixels)
Comctl32.dll version 5.82.2900.2982
Windows XP 5.1 Build 2600 Service Pack 2
Single processor
|
| 3 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Aug 28 2007 : 08:05:21 AM
That's OK, these things happen 
I was wondering if I was supposed to understand that code. Even after a fair bit of experience I come across C++ code that confuses me every now and then |
| cgough |
Posted - Aug 27 2007 : 4:55:34 PM
Doh!
In my rushed state I goofed this up. Thanks for setting me on the right path. Bad day today...
Very very sorry.
Chris
|
| feline |
Posted - Aug 27 2007 : 2:40:49 PM
I am seeing the same thing here, but what is "m_Y"? It is not coloured as a type, but I cannot use it as a type. I added a constructor to the class to test this, and both statements:
m_Y foo;
struct m_Y boo;
fail to compile. Since this seems to suggest it is not a type, why should it be coloured as a type?
This is testing with VS2005. |
