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,642c983bc89db880 X-Google-Attributes: gid103376,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news4.google.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "(see below)" Newsgroups: comp.lang.ada Subject: Re: pragma Pack vs. Convention C, portability issue? Date: Fri, 11 Jan 2008 19:53:05 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Trace: individual.net vm47yVwjFAmpcauYGwsxlAniaFBeDggsIGmVZR23XPIr8ZiYca Cancel-Lock: sha1:ggvWe1nMZEbvNi9sFM90Mv87GK8= User-Agent: Microsoft-Entourage/11.3.6.070618 Thread-Topic: pragma Pack vs. Convention C, portability issue? Thread-Index: AchUi5SU0vGtIMB+EdyDVgARJIjQTg== Xref: g2news1.google.com comp.lang.ada:19326 Date: 2008-01-11T19:53:05+00:00 List-Id: On 11/1/08 04:20, in article fm8e95$q0u$1@jacob-sparre.dk, "Randy Brukardt" wrote: > > Moral: avoid Pack for anything where the representation matters to > portability. Use 'Component_Size instead. What is the view on combinations like this: type seive is array (pos_integral range <>) of Boolean; for seive'component_size use 8; pragma pack(seive); or even this: type a_set is array (a_member) of Boolean; for a_set'Component_Size use 1; pragma Pack(a_set); pragma Convention(C, Entity => a_set); I guess these are somewhat redundant. Does it matter? -- Bill Findlay chez blueyonder.co.uk