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-16 08:26:04 PST Path: archiver1.google.com!postnews1.google.com!not-for-mail From: dewar@gnat.com (Robert Dewar) Newsgroups: comp.lang.ada Subject: Re: Decimal Floating point was RE: Information Systems Annex was RE: Dispatching and generics - language lawyer question Date: 16 Aug 2002 08:26:04 -0700 Organization: http://groups.google.com/ Message-ID: <5ee5b646.0208160726.1f5a807f@posting.google.com> References: NNTP-Posting-Host: 205.232.38.14 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1029511564 16853 127.0.0.1 (16 Aug 2002 15:26:04 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 16 Aug 2002 15:26:04 GMT Xref: archiver1.google.com comp.lang.ada:28110 Date: 2002-08-16T15:26:04+00:00 List-Id: "Robert C. Leif" wrote in message news:... > From: Bob Leif > To: Robert Dewar et al. > > Since Ada has a function Ada.Unchecked_Conversion(S : > Source) return Target; she does permit a change in types. Yes, but with implementation defined effects! 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, Once again Bob, this is compeltely incomprehensible. A "number" is not static or non-static in Ada, an expression is static or non-static. See the rules in 4.9, and please try to express what you have in mind in a comprehensible manner using Ada terminology. If you can't do that, perhaps you can provide a complete, even if vague example, and we might be able to figure out what you have in mind. It seems that you have some confusion between exponent and delta in your mind. They of course are quite different concepts. It is of course possible to change the delta of a number, and if you want variable scaling (perhaps that is what you are talking about) the easiest way is just to use conversions. Remember that fixed point in Ada is nothing more than scaled integer arithmetic. You can always do scaling yourself. So what I would propose you do to illustrate your idea (which may have merit, I can't tell, I don't have the foggiest idea what it is), is to first program it manually doing the scaling yourself. Then imagine some syntactic sugar to help you with the scaling. and illustrate the desired sugar. I do not know > how to do this? > > > -----Original Message----- > From: comp.lang.ada-admin@ada.eu.org > [mailto:comp.lang.ada-admin@ada.eu.org] On Behalf Of Robert Dewar > Sent: Thursday, August 15, 2002 2:32 AM > To: comp.lang.ada@ada.eu.org > Subject: Re: Information Systems Annex was RE: Dispatching and generics > - language lawyer question > > "Robert C. Leif" wrote in message > news:... > > Since virtually all of these decimal types will be > > intermediates in a > > calculation, they could all have the same number of > > digits. > > I really have no idea what the above means. > > > The delta is > > the problem. > > Ditto > > > > My crude workaround was to turn a non-static number into > > a static number by either a pragma or a method. > > And double ditto here. Robert please explain at least vaguely what you > have in mind. What on earth does it mean > to turn a non-static number into a static number. You are > certainly not using the term static in the Ada sense, or > in any other common sense that I can guess. > > > However, I would be happy > > with a decimal floating type. > > This seems to be of very marginal use to me. Certainly not > something to build into the language. If you need such a > facility, just program it, that's easy enough, Yes, it > will be inefficient, but no more or less inefficient than > if it is put in the language, since obviously no machines > support this at the hardware level, and all the compiler > would do is call runtime routines anyway. So all you are > talking about here is a minor bit of syntactic convenience > for a feature with very limited use. Hardly a good candidate for a > language extension.