void *

[kwh at bentley]

In article <194 at 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