With the following in a header file:
typedef struct
{
struct
{
int should_not_see_me;
} should_see_me;
int should_see_me2;
} mytype;
You would expect that "should_not_see_me" would only be visible inside the "should_see_me" structure.
With the following code:
mytype a;
a.
You would expect VAX to show 'should_see_me' & 'should_see_me2', but it shows all members of 'should_see_me also', which is confusing, as they are local to 'should_see_me', and thus not accessible directly from 'a':
VAX shows a padlock on the inaccessible members, so I can only assume that VAX recognises this, but decides to show it anyway? Is this due to misconfiguration at my end?
Topic Locked
Posted - Sep 01 2005 : 06:33:28 AM
