Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site dataioDataio.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!tektronix!uw-beaver!uw-june!entropy!dataio!bright
From: bright@dataioDataio.UUCP (Walter Bright)
Newsgroups: net.lang.c
Subject: Re: malloc()
Message-ID: <1005@dataioDataio.UUCP>
Date: Tue, 27-May-86 13:30:11 EDT
Article-I.D.: dataioDa.1005
Posted: Tue May 27 13:30:11 1986
Date-Received: Fri, 30-May-86 05:18:34 EDT
Reply-To: bright@dataio.UUCP (Walter Bright
Organization: Data I/O Corp., Redmond WA
Lines: 15

In article <3754@sun.uucp> guy@sun.uucp (Guy Harris) writes:
>> I also thought that casting anything into a (void*) would be a big
>> no-no.  Lint, and maybe even the compiler, would issue loud warnings
>> every time one tried to do this.
>> For some perverse reason that I have never been able to understand,
>> X3J11 decided that any pointer could be converted to (void*) without
>> complaint.

Ah, but if you have a function prototype such as:

	extern void free(void *);

and then try to free a pointer to a struct, you are implicitly casting
the struct pointer to a void *. Generating an error on this would
make void * fairly useless.