Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 beta 3/9/83; site frog.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!alberta!ubc-vision!uw-beaver!tektronix!hplabs!pesnta!greipa!decwrl!decvax!ucbvax!ucdavis!lll-crg!seismo!harvard!think!mit-eddie!cybvax0!frog!john
From: john@frog.UUCP (John Woods)
Newsgroups: net.sources.bugs,net.lang.c,net.unix-wizards
Subject: Re: efopen.c (about void voids)
Message-ID: <267@frog.UUCP>
Date: Thu, 24-Oct-85 11:59:46 EST
Article-I.D.: frog.267
Posted: Thu Oct 24 11:59:46 1985
Date-Received: Wed, 30-Oct-85 07:21:13 EST
References: <1741@watdcsu.UUCP> <2109@brl-tgr.ARPA> <796@rlgvax.UUCP> <493@ttrdc.UUCP> <210@l5.uucp>
Distribution: net
Organization: Charles River Data Systems, Framingham MA
Lines: 20
Xref: watmath net.sources.bugs:556 net.lang.c:6877 net.unix-wizards:15513

> I've had it. I'm going to write a book, called *HOW TO WRITE PORTABLE C
> PROGRAMS*.
> 
> #define void int /* remove this line if your compiler knows about void */
> 
Although I am sure that someone has a compiler for which the following will
not make sense, in general the construct

#ifndef lint
#define void int
#endif

allows one to have one's cake and eat it too.

--
John Woods, Charles River Data Systems, Framingham MA, (617) 626-1101
...!decvax!frog!john, ...!mit-eddie!jfw, jfw%mit-ccc@MIT-XX.ARPA

Out of my way, I'm a scientist!
	War of the Worlds