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.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,81bb2ce65a3240c3 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.68.129.9 with SMTP id ns9mr3423459pbb.1.1335377380275; Wed, 25 Apr 2012 11:09:40 -0700 (PDT) Path: r9ni97724pbh.0!nntp.google.com!news2.google.com!goblin1!goblin2!goblin.stu.neva.ru!aioe.org!.POSTED!not-for-mail From: "Zhu Qun-Ying" Newsgroups: comp.lang.ada Subject: Re: What would you like in Ada202X? Date: Wed, 25 Apr 2012 11:10:06 -0700 Organization: Aioe.org NNTP Server Message-ID: References: <3637793.35.1335340026327.JavaMail.geo-discussion-forums@ynfi5> NNTP-Posting-Host: QG+sVfyUW3QoXBz9uF2CgQ.user.speranza.aioe.org Mime-Version: 1.0 X-Complaints-To: abuse@aioe.org User-Agent: Opera Mail/11.62 (Linux) X-Notice: Filtered by postfilter v. 0.8.2 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Date: 2012-04-25T11:10:06-07:00 List-Id: Arbitrary precision of integer and float numbers (in the sense of GMP, MPFR). Specifically to the GNAT case, as GCC include GMP and MPFR to compile itself, it would be nice that gnat pickup this and have the build in mechanism to handle arbitrary precision of numbers. On Wed, 25 Apr 2012 06:10:58 -0700, Nicholas Paul Collin Gloucester wrote: > I would like infinite precision; infinite accuracy; and infinite > speed. In practice, I may need to compromise on at least one of > those. If I resort to a compromise, then I would benefit from being > able to absolutely trivially have different executables of the same > source code which differ in their mathematical implementations (such > as one executable using fixed-point numbers and another executable > exploiting fractions to represent real numbers etc.). I can already > substitute one reification of an abstract datatype by another, but I > want this without any overhead.