Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/3/84; site maynard.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!panda!talcott!wjh12!maynard!campbell
From: campbell@maynard.UUCP (Larry Campbell)
Newsgroups: net.sources.bugs,net.lang.c,net.unix-wizards
Subject: Re: Re: efopen.c (about void voids)
Message-ID: <181@maynard.UUCP>
Date: Fri, 1-Nov-85 22:50:48 EST
Article-I.D.: maynard.181
Posted: Fri Nov  1 22:50:48 1985
Date-Received: Sun, 3-Nov-85 09:44:52 EST
References: <1741@watdcsu.UUCP> <2109@brl-tgr.ARPA> <796@rlgvax.UUCP> <493@ttrdc.UUCP> <210@l5.uucp> <267@frog.UUCP> <1594@hammer.UUCP>
Distribution: net
Organization: The Boston Software Works Inc., Maynard, MA
Lines: 23
Xref: watmath net.sources.bugs:559 net.lang.c:6923 net.unix-wizards:15563

> What doesn't make sense is having a combination of compiler and lint
> where one knows about void and the other doesn't.
> 
> (Sure it's *possible*, but WHY?)
> 
> Snoopy
> tektronix!tekecs!doghouse.TEK!snoopy

Not only is it possible, it's been done, in VENIX.  (Although the

	#ifdef lint
	#define void int
	#endif

hack seems to work well...)

-- 
Larry Campbell                     decvax!genrad
The Boston Software Works, Inc.                 \
120 Fulton St.                 seismo!harvard!wjh12!maynard!campbell
Boston MA 02109                         /       /
                                   ihnp4  cbosgd
ARPA: maynard.UUCP:campbell@harvard.ARPA