typedef'ing void
Richard Draves
draves at harvard.ARPA
Sun Mar 10 21:55:30 AEST 1985
I just discovered that our C compiler (4.2 cc) does not allow
void to be typedef'ed; furthermore, it gives an error message
that I haven't otherwise seen. This suggests that this is its
intended behaviour, and not another void bug.
Is there any reason to disallow new names for void? Is this
a bug or a feature?
Rich
--
"a picture in the head is a gory murder in an art gallery"
-- Stephen Kosslyn
More information about the Comp.lang.c
mailing list