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: a07f3367d7,7b60a2e8329f4e64 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,UTF8 X-Received: by 10.180.74.141 with SMTP id t13mr1027078wiv.5.1359518308786; Tue, 29 Jan 2013 19:58:28 -0800 (PST) Path: i11ni28358wiw.0!nntp.google.com!feeder1.cambriumusenet.nl!feed.tweaknews.nl!85.12.40.139.MISMATCH!xlned.com!feeder7.xlned.com!newsfeed.xs4all.nl!newsfeed4.news.xs4all.nl!xs4all!usenetcore.com!border1.nntp.ams.giganews.com!border4.nntp.ams.giganews.com!border2.nntp.ams.giganews.com!nntp.giganews.com!weretis.net!feeder1.news.weretis.net!news.swapon.de!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail From: Jeffrey Carter Newsgroups: comp.lang.ada Subject: Re: GNAT 4.4.5 Record Bit_Order Endian issues Date: Mon, 21 Jan 2013 22:14:17 -0700 Organization: Also freenews.netfront.net; news.tornevall.net Message-ID: References: <854ni9c319.fsf@stephe-leake.org> Mime-Version: 1.0 Injection-Date: Tue, 22 Jan 2013 05:14:20 +0000 (UTC) Injection-Info: mx04.eternal-september.org; posting-host="656ea2f23126f57fb36504d2d15a002c"; logging-data="2862"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/gxpJja5kbyZlh2x9aWpRNJrNN4wigm9A=" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 In-Reply-To: <854ni9c319.fsf@stephe-leake.org> Cancel-Lock: sha1:MyOsiSkiJG6c6Eq7xpml47SxRlI= Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: 2013-01-21T22:14:17-07:00 List-Id: On 01/21/2013 08:21 PM, Stephen Leake wrote: > > 2/2 > R.C'Position > > {AI95-00133-01AI95-00133-01} If the nondefault bit > ordering applies to the composite type, and if a > component_clause specifies the placement of C, denotes > the value given for the position of the > component_clause; otherwise, denotes the same value as > R.C'Address - R'Address. The value of this attribute is > of the type universal_integer. > > Note the 'otherwise'; that's means the value is R.C'Address - R'Address > only if position is _not_ specified in a rep clause. No. This says if A and B then D; else E; end if; A = "the nondefault bit ordering applies to the composite type" B = "a component_clause specifies the placement of C" D = "denotes the value given for the position of the component_clause" E = "denotes the same value as R.C'Address - R'Address" The negation of "A and B" is "not A or not B". Thus E holds when the default bit ordering applies, even if the position is specified. -- Jeff Carter "To Err is human, to really screw up, you need C++!" Stéphane Richard 63