Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!nrl-cmf!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: register unions
Message-ID: <7333@brl-smoke.ARPA>
Date: 24 Feb 88 14:34:39 GMT
References: <686@cresswell.quintus.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 7

In article <686@cresswell.quintus.UUCP> ok@quintus.UUCP (Richard A. O'Keefe) writes:
>(void*) has to handle the worst case, and is usually much the same as (char*).

As of the last draft proposed ANSI C standard, (void *) and (char *) are
required to have the same representation.  This is to grandfather in
existing programs that use routines like fwrite() that really should
always have received generic pointers, but historically have (correctly)
been fed (char *)s.