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.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,6a8952cbe009f3ed
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
X-Received: by 10.224.17.140 with SMTP id s12mr6116992qaa.3.1359716036563;
        Fri, 01 Feb 2013 02:53:56 -0800 (PST)
X-Received: by 10.49.94.129 with SMTP id dc1mr1122356qeb.22.1359716036538;
 Fri, 01 Feb 2013 02:53:56 -0800 (PST)
Path: 
 k2ni4456qap.0!nntp.google.com!p13no7854094qai.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Fri, 1 Feb 2013 02:53:56 -0800 (PST)
In-Reply-To: <64e3c342-d042-40a2-8a16-b1f0cdff9f16@googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=130.240.232.139;
 posting-account=Rr9I-QoAAACS-nOzpA-mGxtAlZ46Nb6I
NNTP-Posting-Host: 130.240.232.139
References: <db7b4d36-6c49-4501-954e-68ecc55c3d32@googlegroups.com>
 <4905b963-0036-4129-8050-fb26ef0154d6@googlegroups.com>
 <32314026-23ae-45b8-a4c5-e589e7d79de2@googlegroups.com>
 <kdttga$83d$3@dont-email.me>
 <64e3c342-d042-40a2-8a16-b1f0cdff9f16@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <91527f7c-0679-4c21-95c7-a07f3fff265d@googlegroups.com>
Subject: Re: Numerical calculations: Why not use fixed point types for
 everything?
From: Ada novice <shai.lesh@gmx.com>
Injection-Date: Fri, 01 Feb 2013 10:53:56 +0000
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Date: 2013-02-01T02:53:56-08:00
List-Id: <comp.lang.ada>

What about using fixed point number representation for loop counters? It is=
 common for example we have a time index in a program that is increasing wi=
th a value say t:=3D t + 0.01 seconds for each index in a loop. After a whi=
le, the floating-point representation will start failing in accuracy and at=
 time t =3D 0.68 seconds, the number might actually be 0.67999992 for examp=
le.

But a fixed point number representation can avoid this.=20

YC