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 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,8d7393f07c06c5e9
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news1.google.com!npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!nx02.iad01.newshosting.com!newshosting.com!novia!news-xxxfer.readnews.com!news-out.readnews.com!postnews3.readnews.com!not-for-mail
Date: Sun, 29 Aug 2010 07:29:17 -0400
From: "Peter C. Chapin" <chapinp@acm.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
 rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: Another question about fixed point types.
References: <4c7991c8$0$2375$4d3efbfe@news.sover.net>
 <62f49eaf-ed47-47c7-a13a-96ca5750b4e8@y11g2000yqm.googlegroups.com>
In-Reply-To: 
 <62f49eaf-ed47-47c7-a13a-96ca5750b4e8@y11g2000yqm.googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-ID: <4c7a44d1$0$2390$4d3efbfe@news.sover.net>
Organization: SoVerNet (sover.net)
NNTP-Posting-Host: 5bc58871.news.sover.net
X-Trace: 
 DXC=>`8RoALP\gF0gYVRhloIOBK6_LM2JZB_ClXHJXGi>>6I:WUUlR<856OgJk=U_]>;bH=V<hgdPV_4N
X-Complaints-To: abuse@sover.net
Xref: g2news1.google.com comp.lang.ada:13800
Date: 2010-08-29T07:29:17-04:00
List-Id: <comp.lang.ada>

On 2010-08-29 05:02, Phil Thornley wrote:

> With that definition, the largest value that 'Small is allowed to take
> is 2**-10, and the upper bound is between 2**21 and 2**22, so the
> minimum number of bits for the base type will be 33 (which may or may
> not be significant to you).

Using 64 bit integers for computations isn't too scary if it is
necessary for handling my required precision. I'd prefer not to have to
store the values in 64 bits if I can avoid it. It sounds like I might
have to take a little more control over the representation of certain
numeric types than I might ideally like. It's still a little early to be
sure (meaning I'm not going to worry about it until performance
measurements indicate that it's actually a problem). That said, I do
want to at least understand the issues.

> (and if this is SPARK, there's no base type assertion for fixed point
> types...)

I hope this doesn't sound like a stupid question but what do you mean by
"base type assertion." Do you mean 'for Julian_Day'Base use ...'?

Peter