Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2.fluke 9/24/84; site cal-dbb.fluke.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!decvax!tektronix!uw-beaver!fluke!zoro
From: zoro@fluke.UUCP (Mark Hinds)
Newsgroups: net.lang.c
Subject: Re: C Floating point arithmetic
Message-ID: <2464@cal-dbb.fluke.UUCP>
Date: Wed, 27-Nov-85 23:00:54 EST
Article-I.D.: cal-dbb.2464
Posted: Wed Nov 27 23:00:54 1985
Date-Received: Sat, 30-Nov-85 00:37:16 EST
References: <706@lasspvax.UUCP>
Distribution: net
Organization: John Fluke Mfg. Co., Inc., Everett, WA
Lines: 24

In article <706@lasspvax.UUCP> garry%geology@cu-arpa.cornell.edu.arpa writes:
>Pet peeve:
>
>In an inauspicious moment, K&R specified "All floating-point arithmetic
>in C is done in double precision" (pg 41).
>
>Comments? Does everybody agree?
>
>garry wiegand
>
>garry%geology@cu-arpa.cs.cornell.edu

	I can only gues that K&R did not intend C for numerical
	applications. This simplifies expression evaluation code
	generation, and greatly simplifies/reduces the math library
	(look at all the different flavors of math functions in FOTRAN).

	I agree that this is now a problem, it may not have been
	when C was first used. Hopefully ANSI C will resolve this.
-- 
____________________________________________________________
Mark Hinds                     {decvax,ihnp4}!uw-beaver!--\
John Fluke Mfg. Co., Inc.                 {sun,allegra}!---> fluke!zoro
(206) 356-6264                 {ucbvax,hplabs}!lbl-csam!--/