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,
	MSGID_FROM_MTA_HEADER autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 126597,379c1e544eb51c83
X-Google-Attributes: gid126597,public
X-Google-ArrivalTime: 1982-11-02 09:30:08 PST
Message-ID: <bnews.utcsrgv.645>
Newsgroups: net.lang.ada
Path: utzoo!utcsrgv!donald
X-Path: utzoo!utcsrgv!donald
From: utcsrgv!donald
Date: Tue Nov  2 12:30:07 1982
Subject: Re: Fixed point data in Ada
References: <bnews.duke.2719>
X-Google-Info: Converted from the original B-News header
Posted: Tue Nov  2 11:34:15 1982
Received: Tue Nov  2 12:30:07 1982
Date: 1982-11-02T12:30:07+00:00
List-Id: <comp.lang.ada>

What's all the fuss about the fixed-point computation?  Fixed point
numbers are just values which have an absolute error rather than
a relative error as in floating point.  The way that fixed point numbers
in Ada are obviously intended to be implemented is as scaled binary
integers (note the power of two delta), to satisfy the urges of those
that want to perform "real" arithmetic on little microprocessors controlling
cruise missiles that don't have hardware floating-point (and can't take
software floating-point).  Of course, fixed-point computations are
much nastier with regard to error analyses, but as long as that cruise
missile reaches them ruskies...