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,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 2002:a24:610e:: with SMTP id s14-v6mr16361864itc.38.1539685092818; Tue, 16 Oct 2018 03:18:12 -0700 (PDT) X-Received: by 2002:aca:fdc7:: with SMTP id b190-v6mr370415oii.3.1539685092688; Tue, 16 Oct 2018 03:18:12 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.gegeweb.eu!gegeweb.org!usenet-fr.net!proxad.net!feeder1-2.proxad.net!209.85.166.215.MISMATCH!z5-v6no39197ite.0!news-out.google.com!n199-v6ni85itn.0!nntp.google.com!x98-v6no40226ita.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Tue, 16 Oct 2018 03:18:12 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=80.139.103.202; posting-account=rmHyLAoAAADSQmMWJF0a_815Fdd96RDf NNTP-Posting-Host: 80.139.103.202 References: <9d90fa3e-f800-4086-bf97-a65474a8140a@googlegroups.com> <4ddbc9bf-0e2e-466d-8238-d8f709b985e1@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <35f53cd9-4979-49b8-a5df-2c1cf0764507@googlegroups.com> Subject: Re: Examining individual bytes of an integer From: AdaMagica Injection-Date: Tue, 16 Oct 2018 10:18:12 +0000 Content-Type: text/plain; charset="UTF-8" Xref: reader02.eternal-september.org comp.lang.ada:54603 Date: 2018-10-16T03:18:12-07:00 List-Id: Am Montag, 15. Oktober 2018 22:18:16 UTC+2 schrieb Randy Brukardt: > "Niklas Holsti" wrote in message > news:g2k5fbF9thnU1@mid.individual.net... > > On 18-10-15 13:18 , AdaMagica wrote: > >> There is the old Dewar rule that no compiler is doing nonsense. It > >> would be a very unfriendly compiler to not follow this advice. > > > > As I remember it, Dewar's rule says that the Ada *RM* does not specify > > nonsense, meaning that if some reading of the RM seems to be nonsense, it > > is the wrong reading. > > That's correct. > > > I don't remember Dewar saying anything similar about compilers. > > Me either. Compilers do nonsense all of the time (usually not on purpose, > though). OK, I stay corrected. But I still claim that it would be extremely unfair of a compiler not to follow this advice (A'Address = A (A'First)'Address with increasing addresses for further components). I'm apt to try a wager that Randy agrees. Praps I'm gonna lose again... Tant pis!