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.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: getting same output as gfortran, long_float Date: Fri, 1 May 2015 09:45:13 +0200 Organization: cbb software GmbH Message-ID: <142zdljlf0w57.1xh4g0wxv88y8.dlg@40tude.net> References: <1kxou0nloqg9c$.1x0itzgdrlosm$.dlg@40tude.net> <1i8x3r1feyzkt$.j85il7e3wpv9.dlg@40tude.net> Reply-To: mailbox@dmitry-kazakov.de NNTP-Posting-Host: evoS9sCOdnHjo0GRLLMU1Q.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: 40tude_Dialog/2.0.15.1 X-Notice: Filtered by postfilter v. 0.8.2 Xref: news.eternal-september.org comp.lang.ada:25683 Date: 2015-05-01T09:45:13+02:00 List-Id: On Fri, 01 May 2015 02:32:27 -0500, Nasser M. Abbasi wrote: > Actually, it is much more complicated. The way I wrote it > above is not the optimal way. One is supposed to call > SELECTED_REAL_KIND(n,e) requesting n significant digits > and e number of digits in the exponent (e is optional). Huh, they finally learned something after half of a century! (:-)) > i.e. one is supposed to write > > SELECTED_REAL_KIND(8,3) specifies real type of > (+-) 0.xxxxxxxx * 10 ^(+-)xxx > > If the compiler does not support this, then the compile > will fail. This is in a way similar to Ada's > > type my_type is digits n; Yes, though Ada also mandates that for the precision specified, the implementation must guarantee certain accuracy of operations. Maybe in the following 50 years FORTRAN will get that idea as well. > And it is supposed to be portable way of doing things, vs. > using Real*16. Actually REAL*16 is exactly portable. The problem addressed is not portability, it is rather design being driven by requirements from the problem space rather than from implementation specific aspects. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de