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,1de1981df403322c X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-11-09 06:34:32 PST Path: archiver1.google.com!postnews1.google.com!not-for-mail From: martin.dowie@btopenworld.com (Martin Dowie) Newsgroups: comp.lang.ada Subject: Re: New limited range type? Date: 9 Nov 2003 06:34:32 -0800 Organization: http://groups.google.com Message-ID: References: <20619edc.0311071005.15e6b9a8@posting.google.com> NNTP-Posting-Host: 20.138.254.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1068388472 8516 127.0.0.1 (9 Nov 2003 14:34:32 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Sun, 9 Nov 2003 14:34:32 +0000 (UTC) Xref: archiver1.google.com comp.lang.ada:2282 Date: 2003-11-09T06:34:32-08:00 List-Id: Nick Roberts wrote in message news:... > I have an alternative proposal: a new language-defined attribute Conform, > which would be applicable to any fixed-point subtype S, and would be a > function with the profile: > > function S'Conform (X: in universal_real) return S; I can cope with that - although I don't like the name much. How about: function S'Limit (X:... [snip] > Note how I define a fixed point type to provide a big enough base range (in > this case 50 complete turns either way) for all calculations, and then a > subtype of it to define the required confined or normalised range. While that's good technique, I presume your NOT saying that the RM would require this? Also, why not allow it for any scalar type? -- Martin