Path: utzoo!mnetor!uunet!husc6!uwvax!oddjob!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.lang.c
Subject: Re: Bug in new K&R?
Message-ID: <11404@mimsy.UUCP>
Date: 7 May 88 13:51:56 GMT
References: <44200009@uicsrd.csrd.uiuc.edu>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 12
Summary: dpANS says (void *) \equiv (char *)

In article <44200009@uicsrd.csrd.uiuc.edu> mcdaniel@uicsrd.csrd.uiuc.edu asks:
>Are those two casts portable---is it guaranteed that "void *" and
>"char *" have the same internal representation?

It is so guaranteed, according to the most recent public draft
review standard.

In the dpANS, `void *' is simply a notational convenience for
`char * but_never_complain_about_mixed_pointer_types'.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris