Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site l5.uucp
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!lll-crg!well!l5!gnu
From: gnu@l5.uucp (John Gilmore)
Newsgroups: net.lang.c,net.sources.bugs
Subject: Making voids work portably (was re: efopen.c)
Message-ID: <202@l5.uucp>
Date: Mon, 21-Oct-85 02:14:31 EDT
Article-I.D.: l5.202
Posted: Mon Oct 21 02:14:31 1985
Date-Received: Tue, 22-Oct-85 06:25:23 EDT
References: <1741@watdcsu.UUCP> <2109@brl-tgr.ARPA> <796@rlgvax.UUCP> <493@ttrdc.UUCP>
Organization: Nebula Consultants, San Francisco
Lines: 10
Xref: watmath net.lang.c:6799 net.sources.bugs:534
Summary: Write the code portably, add -Dvoid=int on broken systems

In article <493@ttrdc.UUCP>, levy@ttrdc.UUCP (Daniel R. Levy) writes:
> (void)whatever is not supported at all under VAX/VMS C.  It will barf
> severely on (originally) Unix C programs which have been heavily larded with
> (void)'s for the sake of lint.  Not the entire C world is Unix.

Void is well defined and pretty easily portable, though it's true that
many compilers don't fully implement it.  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...