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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,18f7f6e041b3e0bf X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-08-15 23:26:13 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!bloom-beacon.mit.edu!howland.erols.net!usc.edu!newspeer.cts.com!galanthis.cts.com!127.0.0.1.MISMATCH!not-for-mail Sender: kst@king.cts.com Newsgroups: comp.lang.ada Subject: Re: Decimal Floating point was RE: Information Systems Annex was RE: Dispatching and generics - language lawyer question References: From: Keith Thompson Date: 15 Aug 2002 23:26:11 -0700 Message-ID: X-Newsreader: Gnus v5.7/Emacs 20.7 NNTP-Posting-Host: 209.68.192.180 X-Trace: 1029479171 nntp.cts.com 321 209.68.192.180 Xref: archiver1.google.com comp.lang.ada:28084 Date: 2002-08-15T23:26:11-07:00 List-Id: "Robert C. Leif" writes: > Since intermediate values in a calculation how a low frequency of being > printed out, the simplest solution to digits is to leave it at a fixed > value, which will usually be the maximum number of digits allowed. This > simplifies the use of precompiled datatypes. Only one for each value of > digits needs to be created. > > Since Ada has a function Ada.Unchecked_Conversion(S : Source) return > Target; she does permit a change in types. In the case of the delta, I > am proposing what I hope is much less extreme. I want to tell the > compiler to accept a non-static number as a static number. Since this is > not a type change but the change of a property of a type, I do not know > how to do this? You "want to tell the compiler to accept a non-static number as a static number". That barely even makes sense, and I don't believe it's what you really need. You're saying you want to use a non-static value in a context where the language requires a static value. Coercing the compiler to accept a non-static value in such a context is not a "much less extreme" way to do this, and a pragma is not an appropriate way to specify it. I think you're jumping from what you want to be able to do to a proposed implementation. Unfortunately, the implementation you're proposing is not workable. What problem are you trying to solve? -- Keith Thompson (The_Other_Keith) kst@cts.com San Diego Supercomputer Center <*> Schroedinger does Shakespeare: "To be *and* not to be"