Must a NULL pointer be a 0 bit patte

Henry Spencer henry at utzoo.UUCP
Tue Nov 6 09:53:05 AEST 1984

> What is wrong with
> 	union foo thing.member = {...};
> ?  It is clear and unambiguous.

I could mumble about irregular syntax and lack of implementation experience,
but this particular suggestion doesn't sound bad.  It eliminates the problems
of trying to guess a member name from a (possibly incomplete) indication of
type, and I don't *think* it would break anything.  The remaining questions
are (a) is it needed badly enough to bother?, and (b) can the ANSI folks be
convinced of this?  [Note that convincing me doesn't help; despite my habit
of taking the committee's side, I'm not a member of it.]
				Henry Spencer @ U of Toronto Zoology

More information about the Comp.lang.c mailing list