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,dcab94c78b71ea2b
X-Google-Attributes: gid103376,public
From: Robert A Duff <bobduff@world.std.com>
Subject: Re: Fixed Point Numbers
Date: 1999/06/08
Message-ID: <wcc909uhbdb.fsf@world.std.com>#1/1
X-Deja-AN: 487141631
Sender: bobduff@world.std.com (Robert A Duff)
References: <374DBCE1.9FB720E6@mitre.org>
Organization: The World Public Access UNIX, Brookline, MA
Newsgroups: comp.lang.ada
Date: 1999-06-08T00:00:00+00:00
List-Id: <comp.lang.ada>

"Robert I. Eachus" <eachus@mitre.org> writes:

>     In both cases you should get exactly the same representation, and
> operations that use hardware overflow to do range checking, although you
> may (or may not) get different values for 'Last.  The definition of
> fixed point types cleverly does not require that the end points of the
                    ^^^^^^^^
> specified range be values of the (sub)type. ...

You misspelled "confusingly".  ;-)

After all, I don't expect this:

    type T is range -2**31..2**31;

to fit in 32 bits!

- Bob
-- 
Change robert to bob to get my real email address.  Sorry.