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!columbia!topaz!ll-xn!nike!ucbcad!ucbvax!SIERRA.STANFORD.EDU!Mendal
From: Mendal@SIERRA.STANFORD.EDU (Geoff Mendal)
Newsgroups: net.lang.ada
Subject: The AFT Attribute
Message-ID: <12239247219.20.MENDAL@Sierra.Stanford.EDU>
Date: Mon, 15-Sep-86 20:32:59 EDT
Article-I.D.: Sierra.12239247219.20.MENDAL
Posted: Mon Sep 15 20:32:59 1986
Date-Received: Tue, 16-Sep-86 21:02:45 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
List-Id: <comp.lang.ada>

Hello Ada Fans,

I'm confused again.  In the LRM, 3.5.10(9) states (parenthetically)
that the value of the AFT attribute is the smallest positive N
such that (10 ** N) * T'DELTA >= 1.0.  Now, 3.5.10(15) states that
the value returned by AFT depends only on T'DELTA. [3.5.10(15) is
a "note".]

Can these two paragraphs imply a cohesive semantics for the AFT
attribute?  Using 3.5.10(9) on the following type:

  type Fix is delta 1.0 / 16.0 range 0.0 .. 1.0;

The smallest value N that satisfies the equation is 2.  But how can
one represent 1.0 / 16.0 accurately in two decimal digits?
[1.0 / 16.0 = 0.0625]

What am I missing here?

gom
-------