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:2752:: with SMTP id
 g79-v6mr11744574ita.4.1539560560084;
        Sun, 14 Oct 2018 16:42:40 -0700 (PDT)
X-Received: by 2002:a9d:3d06:: with SMTP id a6mr138784otc.0.1539560559808;
 Sun, 14 Oct 2018 16:42:39 -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-v6no398164ite.0!news-out.google.com!n199-v6ni416itn.0!nntp.google.com!x98-v6no400564ita.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Sun, 14 Oct 2018 16:42:39 -0700 (PDT)
In-Reply-To: <9d90fa3e-f800-4086-bf97-a65474a8140a@googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=24.34.53.181;
 posting-account=1tLBmgoAAAAfy5sC3GUezzrpVNronPA-
NNTP-Posting-Host: 24.34.53.181
References: <9d90fa3e-f800-4086-bf97-a65474a8140a@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <4f2fb3ba-9cca-46ad-b970-ccbcb7d08a2c@googlegroups.com>
Subject: Re: Examining individual bytes of an integer
From: Matt Borchers <mattborchers@gmail.com>
Injection-Date: Sun, 14 Oct 2018 23:42:40 +0000
Content-Type: text/plain; charset="UTF-8"
Xref: reader02.eternal-september.org comp.lang.ada:54570
Date: 2018-10-14T16:42:39-07:00
List-Id: <comp.lang.ada>

Does anybody ever do this kind of thing?

procedure Main is

   type Byte is mod 256;
   type Word is mod 2 ** 32;

   type E2 is array(1 .. 4) of Byte;
   
   Z: Word;
   Y: E2;
   for Y'Address use Z'Address;

begin
   --here you can reference Z or Y directly.
   --two types overlaid on the same memory location.
   --of course if it matters, you still have to know the endian to know if Y(1) or Y(4) is the low-order byte of Z.
end Main;