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,544e7f5698c48b7c
X-Google-Attributes: gid103376,public
From: Matthew Heaney <matthew_heaney@acm.org>
Subject: Re: precise floats
Date: 1998/08/05
Message-ID: <m3g1fcmvp6.fsf@mheaney.ni.net>#1/1
X-Deja-AN: 378007546
Sender: matt@mheaney.ni.net
References: <6q7vtb$jk$1@heliodor.xara.net>
NNTP-Posting-Date: Tue, 04 Aug 1998 18:41:43 PDT
Newsgroups: comp.lang.ada
Date: 1998-08-05T00:00:00+00:00
List-Id: <comp.lang.ada>

"Bob Fletcher" <bob@radge.nospam.globalnet.co.uk> writes:

> What is the best way to define a float type that has greater precision,
> (like a lot greater), than the default one? Is there a simple way to do
> this?

How about

   type Max_Float is digits System.Max_Digits;

Is that what you had in mind?