Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ucla-cs.ARPA
Path: utzoo!linus!decvax!ittatc!dcdwest!sdcsvax!sdcrdcf!ucla-cs!jimc
From: jimc@ucla-cs.UUCP
Newsgroups: net.lang.c
Subject: Re: C Floating point arithmetic
Message-ID: <7934@ucla-cs.ARPA>
Date: Mon, 9-Dec-85 17:39:58 EST
Article-I.D.: ucla-cs.7934
Posted: Mon Dec  9 17:39:58 1985
Date-Received: Wed, 11-Dec-85 22:06:54 EST
References: <706@lasspvax.UUCP> <7849@ucla-cs.ARPA> <322@brl-tgr.ARPA>
Reply-To: jimc@ucla-cs.UUCP (Jim Carter)
Distribution: net
Organization: UCLA Computer Science Department
Lines: 14

In article <322@brl-tgr.ARPA> gwyn@brl-tgr.ARPA (Doug Gwyn <gwyn>) writes:
>> K+R says you can convert any pointer to an int and back again without
>> wrecking it.
>
>That is NOT what it says.

Mea culpa.  K+R A.14.4 (p.210) para. 2 says "Whether an int or a long is
required is machine dependent."  I was remembering the next paragraph, which
says that an "integer" converted from a pointer can be converted back to
the same pointer.

James F. Carter            (213) 206-1306
UCLA-SEASnet; 2567 Boelter Hall; 405 Hilgard Ave.; Los Angeles, CA 90024
UUCP:...!{ihnp4,ucbvax,{hao!cepu}}!ucla-cs!jimc  ARPA:jimc@locus.UCLA.EDU