C Compiler bug (and fix for a different one)

[Alan Curtis]

In article <134 at sas.UUCP> jcz at sas.UUCP (Carl Zeigler) writes:
>
>  In article <5858 at alice.uUCp>, ark at alice.UucP (Andrew Koenig) writes:
>  > > So, does anyone have a fix for this bug?
>  > > 
>  > > void f3(which)
>  > > {
>  > >     extern void f1(),f2();
>  > >     which?f1():f2();
>  > > }
>  > > cc(1) gives an "incompatible types" error.
>  > 
>  > As it should.  The only thing you're allowed to do with void values
>  > is throw them away.
>
>
>Scan again, Andrew, the (void) values are being thrown away.
>
No, the value of the statement is being thrown away, not the value
of the void(s).

Would you let me say:
	.
	.
	.
	f1() + f2();
	.
	.

Since I am throwing both away?
Alan Curtis