Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/12/84; site desint.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!mhuxn!mhuxr!ulysses!allegra!mit-eddie!think!harvard!seismo!lll-crg!ucdavis!ucbvax!decvax!ittatc!dcdwest!sdcsvax!sdcrdcf!trwrb!desint!geoff
From: geoff@desint.UUCP (Geoff Kuenning)
Newsgroups: net.lang.c
Subject: Re: Making voids work portably (was re: efopen.c)
Message-ID: <131@desint.UUCP>
Date: Sat, 26-Oct-85 22:53:06 EST
Article-I.D.: desint.131
Posted: Sat Oct 26 22:53:06 1985
Date-Received: Wed, 30-Oct-85 04:28:57 EST
References: <796@rlgvax.UUCP> <493@ttrdc.UUCP> <202@l5.uucp>
Reply-To: geoff@desint.UUCP (Geoff Kuenning)
Organization: SAH Consulting, Manhattan Beach, CA
Lines: 16

In article <202@l5.uucp> gnu@l5.uucp (John Gilmore) writes:

>  If you write the code
>with void, it can be trivially made to work on systems without broken voids
>by adding COPTS='-Dvoid=int' to the Makefile -- without source changes.
>*That*'s portability...

Actually, the safest thing is to use VOID, not void, and use either
-DVOID=void or -DVOID=int on your cc line.  I've used a compiler (Mark
Williams C-86) where voids had severe problems (e.g., the no-pointer-to-
void-functions bug), but the built-in preprocessor wouldn't let me use
-Dvoid=int because void was a keyword it knew!  A quick edit fixed all that.
-- 

	Geoff Kuenning
	{hplabs,ihnp4}!trwrb!desint!geoff