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-Thread: 103376,f9957894e0bdf128 X-Google-Attributes: gid103376,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!postnews.google.com!n41g2000yqh.googlegroups.com!not-for-mail From: Adam Beneschan Newsgroups: comp.lang.ada Subject: Re: How to put 200 into an integer sub-type of 16 bits (code included) Date: Thu, 15 Jan 2009 17:17:32 -0800 (PST) Organization: http://groups.google.com Message-ID: <3b742adc-bbe7-4423-882e-6ca900671262@n41g2000yqh.googlegroups.com> References: <407ae64d-3cb3-4310-b59e-f1bbae9910a5@t39g2000prh.googlegroups.com> <71gqm49eatq868htrvd7eghm3m8su8kcbl@4ax.com> <7b017de2-951a-414a-8290-111353fe02f8@r15g2000prd.googlegroups.com> <46075a57-3445-44ae-b40e-dcad9e0e1fcf@v18g2000pro.googlegroups.com> <3d951e6e-c87d-4667-94ab-fcb312288e1d@r37g2000prr.googlegroups.com> <12837a65-dd6e-493f-91e8-4140d67237c2@z28g2000prd.googlegroups.com> <44178c17-a27b-48ff-8ff1-17d04d362ce4@a26g2000prf.googlegroups.com> NNTP-Posting-Host: 66.126.103.122 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: posting.google.com 1232068653 27739 127.0.0.1 (16 Jan 2009 01:17:33 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Fri, 16 Jan 2009 01:17:33 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: n41g2000yqh.googlegroups.com; posting-host=66.126.103.122; posting-account=duW0ogkAAABjRdnxgLGXDfna0Gc6XqmQ User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.7.12-1.3.1,gzip(gfe),gzip(gfe) Xref: g2news2.google.com comp.lang.ada:4337 Date: 2009-01-15T17:17:32-08:00 List-Id: On Jan 15, 1:21 pm, Robert A Duff wrote: > Adam Beneschan writes: > > Wow, that's confusing when looking at 13.1(8). That says, "A > > representation item that names a subtype is either subtype-specific > > (Size and Alignment clauses) or type-related (all others). Subtype- > > specific aspects may differ for different subtypes of the same type". > > It says the "aspects may differ". That is, different subtypes can have > different sizes and alignments. It does not say that you can specify > different sizes and alignments. Yeah, but coming right after, and in the same paragraph as, a sentence that says that "Size and Alignment clauses" are subtype-specific clauses while all others are type-related, how the heck else is one supposed to interpret it? I mean, if the RM goes to all the trouble of distinguishing "subtype-specific rep items" from "type-related rep items", wouldn't one assume that there's some actual reason for making this distinction---and that the sentence that immediately follows it provides that reason? Furthermore, the first two sentences of the paragraph are about representation items, not about aspects; it would seem odd to throw in a sentence about aspects that doesn't have any relevance for representation items. To sum up, I believe that anyone who reads 13.1(8) would think it's 100% clear that subtype-specific representation items can be used to make subtype-specific aspects different for different subtypes of the same type, UNLESS you interpret the paragraph in a VERY odd way. I now see that other clauses in the RM require 13.1(8) to be interpreted in this odd way. But to me, that's an indication that some rewording would be useful. -- Adam