Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!execu!sequoia!rpp386!woody
From: woody@rpp386.cactus.org (Woodrow Baker)
Newsgroups: comp.lang.c
Subject: Re: (void *)  ?  /* again */
Summary: generic pointer
Message-ID: <17712@rpp386.cactus.org>
Date: 21 Jan 90 04:53:51 GMT
References: <6200009@ux1.cso.uiuc.edu>
Organization: River Parishes Programming, Plano, TX
Lines: 23

In article <6200009@ux1.cso.uiuc.edu>, phil@ux1.cso.uiuc.edu writes:
> 
> I have read (but I'm not sure where, I think it was in H&S) that when you
> have the type   (void *)  then its effectively matches any pointer.  For
> instance, malloc is declared like:

I believe in the new ANSI standard it is called a "generic" pointer, but
I'm not certain, as I don't have my Standards draft notes handy.  A nice
little book from PLUM HALL, written by Thomas Plum.  Well worth the $10.00e

you might try something like


#define void int

I have seen some code done this way in order to make it compatible
with a compiler that did not support void.
Watch it carefully however.  Make certain that ints are what you want.
e
> How can I suppress the "void" warnings and keep others w/o having to have
> casts all over my code?
Cheers
Woody