Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ut-sally!husc6!harvard!panda!genrad!decvax!mcnc!rti-sel!sas!jcz
From: jcz@sas.UUCP (Carl Zeigler)
Newsgroups: net.lang.c,net.bugs
Subject: Re: C Compiler bug (and fix for a different one)
Message-ID: <134@sas.UUCP>
Date: Tue, 29-Jul-86 08:52:06 EDT
Article-I.D.: sas.134
Posted: Tue Jul 29 08:52:06 1986
Date-Received: Thu, 31-Jul-86 01:58:02 EDT
References: <273@watmath.UUCP> <5858@alice.uUCp>
Organization: SAS Institute Inc. Cary, NC
Lines: 23
Summary: read before you flame
Xref: mnetor net.lang.c:5496 net.bugs:298


  In article <5858@alice.uUCp>, ark@alice.UucP (Andrew Koenig) writes:
  > > So, does anyone have a fix for this bug?
  > > I'll trade for a fix for a problem with void functions and the ?: operator
  > > 
  > > 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.

-- 
John Carl Zeigler         "Just once I'd like to meet an alien menace
SAS Institute Inc.            that wasn't impervious to bullets !"
Cary, NC  27511
(919) 467-8000			...!mcnc!rti-sel!sas!jcz