Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!ittatc!dcdwest!sdcsvax!sdcrdcf!hplabs!hpda!hpisoa2!hpitg!bentley!kwh@bentley
From: kwh@bentley
Newsgroups: net.lang.c
Subject: Re: void *
Message-ID: <766@bentley>
Date: Tue, 29-Apr-86 01:16:00 EDT
Article-I.D.: bentley.766
Posted: Tue Apr 29 01:16:00 1986
Date-Received: Tue, 13-May-86 00:26:52 EDT
References: <728@bentley>
Lines: 17

In article <194@gilbbs.UUCP> gilbbs!mc68020 writes:
>   Well, that's just great!  The C compiler on my system doesn't understand
>such niceties as void.  So what do we do?  (do *NOT* tell me to get another
>compiler, there *IS* no other compiler available for this system!)

What I've done in the past is "typedef int void;" or "cc -Dvoid=int" when
trying to port new code to old compilers.  Now suddenly void takes on a
new meaning.  Hmm, I'd say your best bet (other than getting a compiler
that understands at least the current standard) is to process any such
sources with a sed script (or something smarter) to change "void *" to
"char *" and other "void" to "int".

Actually, I don't think "void *" will start showing up in programs for
a while after it becomes "standard".  Maybe someone will upgrade your
compiler in the meantime?

Karl W. Z. Heuer (ihnp4!bentley!kwh), The Walking Lint