> Yes, but in my example - sorry - "NeverDefined" doesn't mean "declared and > defined elsewhere (or not)" but "not declared .and. not defined".
no and yes.
union U
{
struct
{
struct NeverDefined nf; // Unknown, definition
not #included
} S1
};
declares a struct named NeverDefined just by mentioning it.
the compiler should reject the use because NeverDefined
is not defined. it's just a bug. i don't have a copy of the
compiler to play with but erik's patch seems fine.
russ
