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=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ut-sally!husc6!necntc!ames!ucbcad!ucbvax!SIERRA.STANFORD.EDU!Mendal
From: Mendal@SIERRA.STANFORD.EDU (Geoff Mendal)
Newsgroups: comp.lang.ada
Subject: Re: Fixed point reals
Message-ID: <12283010785.21.MENDAL@Sierra.Stanford.EDU>
Date: Sun, 1-Mar-87 18:13:25 EST
Article-I.D.: Sierra.12283010785.21.MENDAL
Posted: Sun Mar  1 18:13:25 1987
Date-Received: Tue, 10-Mar-87 22:21:34 EST
References: <MS.V3.18.km38.80021108.allentown.ibm032.3469.1@andrew.cmu.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
List-Id: <comp.lang.ada>

All fixed point types must specify a range constraint, in addition
to a "delta" accuracy.  See ARM 3.5.9(3).  Note that the range
constraint is optional for fixed point SUBTYPES.

The reason for requiring the range constraint on the fixed type
definition is that the underlying model numbers are "computed"
using both the delta accuracy and the range constraint.  For a
floating point type definition, model numbers are computed solely
by the digits accuracy, hence the reason why a range constraint
is not required for a floating point type definition.

gom
-------