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,7b60a2e8329f4e64 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit X-Received: by 10.180.74.79 with SMTP id r15mr4466858wiv.4.1358894404551; Tue, 22 Jan 2013 14:40:04 -0800 (PST) MIME-Version: 1.0 Path: i11ni13941wiw.0!nntp.google.com!proxad.net!feeder1-2.proxad.net!weretis.net!feeder4.news.weretis.net!nuzba.szn.dk!news.jacob-sparre.dk!munin.jacob-sparre.dk!pnx.dk!.POSTED!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: GNAT 4.4.5 Record Bit_Order Endian issues Date: Tue, 22 Jan 2013 16:40:01 -0600 Organization: Jacob Sparre Andersen Research & Innovation Message-ID: References: <854ni9c319.fsf@stephe-leake.org> NNTP-Posting-Host: static-69-95-181-76.mad.choiceone.net X-Trace: munin.nbi.dk 1358894403 24993 69.95.181.76 (22 Jan 2013 22:40:03 GMT) X-Complaints-To: news@jacob-sparre.dk NNTP-Posting-Date: Tue, 22 Jan 2013 22:40:03 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Date: 2013-01-22T16:40:01-06:00 List-Id: "Stephen Leake" wrote in message news:854ni9c319.fsf@stephe-leake.org... > "Randy Brukardt" writes: ... >Note the 'otherwise'; that's means the value is R.C'Address - R'Address >only if position is _not_ specified in a rep clause. Right, because if it is specified you use that value. But it *always* means R.C'Address - R'Address, whether it is specified or not; it's only that the *value* comes from the specification if there is one. So I take it you are complaining about a misplaced "otherwise". I'd suggest you write up an Ada-Comment so it gets onto the agenda of the ARG to fix next time. (I personally think it is obvious, so I wouldn't worry about it, but people differ.) ... >>>> > I agree that the RM is confusing in this area. >>>> > It's partly my fault. :-( >>>> Ok. What paragraphs do we add? (in five years; better late than never >>>> :) >> >> I don't think there is anything that would help. We surely tried when we >> created the non-default bit order stuff. > > Do you think Cohen's paper makes it clear? I gather not. Why not? I read that paper three or four times and never understood any of it. The discussion of "machine scalars" in the AI and in the RM (and especially during the ARG meetings) makes more sense to me than anything in Cohen's paper -- and in all honesty, that isn't intuitive, either. In any case, the Cohen paper is far too long to be used as part of the RM, and it surely defies condensation into a few easily understandable paragraphs. (If someone can do that, I'd welcome adding it to the AARM, I surely couldn't and I tried.) > If that's too complex to put in the RM, maybe the implementation advice > could include a reference to a copy of Cohen's paper on the adaic > website (somehow I doubt ISO standards allow web references). It's referenced from the AI, but as I said, I don't think it helps all that much. Randy.