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 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,b5627b980414da76 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1995-03-14 08:30:06 PST Newsgroups: comp.lang.ada From: davea@linkmsd.com (David Arno) Path: bga.com!news.sprintlink.net!pipex!peernews.demon.co.uk!linkmsd.com!davea Subject: Re: Higher precision and generics Distribution: world References: <3jsnbf$ido@nef.ens.fr> Organization: Thomson Training & Simulation Ltd Reply-To: davea@linkmsd.com X-Newsreader: Demon Internet Simple News v1.29 X-Posting-Host: linkmsd.demon.co.uk Date: Tue, 14 Mar 1995 16:13:26 +0000 Message-ID: <795197606snz@linkmsd.com> Sender: usenet@demon.co.uk Date: 1995-03-14T16:13:26+00:00 List-Id: In article <3jsnbf$ido@nef.ens.fr> sands@clipper.ens.fr "Duncan Sands" writes: : I am writing a package of matrix routines (in Ada!) in which some intermediate : results : should be calculated in higher precision than normal. The type for normal : precision is : called Real and is a generic parameter of my package: : generic : type Real is digits <>; : package Matrix_Stuff is : ... : end; : : In the body I would like to be able to declare Double to be a higher precision : floating point type, something like: : package body Matrix_Stuff is : type Double is digits 2*Real'Digits; : ... : end; : : Unfortunately, this does not compile: apparently formal types like Real are not : considered static, so Real'Digits is not considered static, and only static : expressions are allowed in a "type X is digits expression" declaration. (If : I write "type Double is digits 2*Float'Digits" then it compiles fine). : : What can I do to get type Double to be of higher precision than Real? : Can anyone please help? And does anyone know why formal types like Real are not: considered static? : : Thanks a lot, : : Duncan Sands. : Probably the best thing to do in this situation is to declare a type within the package body which has the highest precision possible: type Max_Precision_type is digits System.Max_digits; and to use that internaly. Even if there were a way of overcoming the need for the expression after digits to be statis, the concept of your internal one always being double the precision of the parameter type falls down if an instance of the package is declared using any type where the number of digits is greater than half the maximum. Hope this helps, -- David Arno