Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site brl-tgr.ARPA
Path: utzoo!linus!decvax!ittvax!dcdwest!sdcsvax!sdcrdcf!hplabs!hao!seismo!brl-tgr!gwyn
From: gwyn@brl-tgr.UUCP
Newsgroups: net.lang.c
Subject: Re: Shouldn't this work?
Message-ID: <4401@brl-tgr.ARPA>
Date: Tue, 4-Sep-84 10:54:59 EDT
Article-I.D.: brl-tgr.4401
Posted: Tue Sep  4 10:54:59 1984
Date-Received: Sun, 16-Sep-84 07:02:27 EDT
References: <347@zeus.UUCP> <4282@brl-tgr.ARPA>, <178@zinfandel.UUCP>
Organization: Ballistics Research Lab
Lines: 9

In currently available C implementations, (void *) data are illegal.
However, (void (*)()) data are legal and quite useful (too bad they
break older versions of PCC).

The proposed use of (void *) in the future C standard is as a generic
pointer, such as malloc(3) should return; one that can be cast into
a pointer to any other datum.  To date this r^ole has been served
by (char *), although that was not the intended use of (char *) and
one desires a separation of these types (for "lint" etc.).