From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,a1d5d5934367929d
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: fixed point vs floating point (When do you use it ?)
Date: 1997/11/27
Message-ID: <dewar.880662487@merv>#1/1
X-Deja-AN: 293228997
References: <65kgtt$289@lotho.delphi.com>
X-Complaints-To: usenet@news.nyu.edu
X-Trace: news.nyu.edu 880662617 17665 (None) 128.122.140.58
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1997-11-27T00:00:00+00:00
List-Id: <comp.lang.ada>


tmoran says

<<A stocks & commodities database I know of uses fixed point.  Stocks have a
delta of 1/8 (though that is supposed to change to decimal soon) and
different commodities have a bunch of different deltas.
>>

The fact that stocks have a delta of 1/8 is NOT a good reason to choose
fixed-point over floating-point for the representation of these values.
In practice all stock values will be model numbers of any reasonable
floating-point type, so the issue of accurate representation does not 
arise. What is important is the computations that you propose to perform
on these values. I would guess that for most purposes, it is better to
use floating-point for stock prices than fixed-point (of course if you
are in COBOL, you have little choice, and indeed stock prices don't fit
nicely into COBOL, which has no provision for binary fixed-point).