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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,b14cbbd362590ac9 X-Google-Attributes: gid103376,public From: Tucker Taft Subject: Re: Rep-spec question Date: 1999/11/10 Message-ID: <3829E153.F05C89B0@averstar.com>#1/1 X-Deja-AN: 547057313 Content-Transfer-Encoding: 7bit Sender: news@inmet.camb.inmet.com (USENET news) X-Nntp-Posting-Host: houdini.burl.averstar.com References: <80ck3b$deu$1@nnrp1.deja.com> X-Accept-Language: en Content-Type: text/plain; charset=us-ascii Organization: AverStar (formerly Intermetrics) Burlington, MA USA Mime-Version: 1.0 Newsgroups: comp.lang.ada Date: 1999-11-10T00:00:00+00:00 List-Id: Joe Wisniewski wrote: > > Given the following: > > type Rec is > b : boolean; > end record; > > for rec use record > b at 0 range 0..63; > end record; > for rec'size use 64; > > can any assumptions be made as to where the > byte(s) representing the boolean are stored? You can pretty safely assume that an enumeration value is stored in the low-order bits of the 64-bit component you have specified. I would expect this only to be supported on implementations that support 64-bit integers. Another interesting question is what are the representations of False and True. I suspect that on some targets, True is all ones, while False is zero. On such a target, the answer to your question is "any byte". ;-) > > Joe -Tuck -- -Tucker Taft stt@averstar.com http://www.averstar.com/~stt/ Technical Director, Distributed IT Solutions (www.averstar.com/tools) AverStar (formerly Intermetrics, Inc.) Burlington, MA USA