🚀 go-pugleaf

In article <1992Aug11.202135.28878@ugle.unit.no> toriver@flipper.pvv.unit.no (Tor Iver Wilhelmsen) writes:
>In article <1992Aug10.031337.4424@druid.uucp> darcy@druid.uucp (D'Arcy J.M. Cain) writes:
>>Gnu C with -Wall -ansi -pedantic has a pretty tight sphincter.

[Additional tightening recommended by other posters.]

>May be, but it still insists on assigining a size of 1 (one) to the type void,
>which according to the parts of the standards I have seen, is an incomplete
>type.  Thus you get a warning:
>void.c:3: warning: sizeof applied to a void type
>but in the resulting output of the sample program, it writes:
>Size of void = 1

Yes, you get a correct diagnostic, and the implementation can then proceed
however it likes on your undefined program.

>c89 under ULTRIX, however, says (same program):
>void.c:3: error: In this statement, "void" is an incomplete type, and so has
>no size.
>Compilation terminated with errors.

Yes, you get a correct diagnostic, and the implementation can then proceed
however it likes on your undefined program.

>which I would think would be right.

You can modify the source for GCC to change its warnings to errors and
terminate compilation.  This would not change its degree of conformance.
--
Norman Diamond       diamond@jit081.enet.dec.com
If this were the company's opinion, I wouldn't be allowed to post it.
"Yeah -- bad wiring.  That was probably it.  Very bad."