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,XPRIO
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,ebc19d379b37caae,start
X-Google-Attributes: gid103376,public
From: "Bruce Detter" <bruce.detter@lmco.com>
Subject: Type size vs. actual size difference.
Date: 2000/03/20
Message-ID: <8b5hhp$pvv1@svlss.lmms.lmco.com>#1/1
X-Deja-AN: 599979109
X-Priority: 3
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Organization: Lockheed Martin Corporation
X-MSMail-Priority: Normal
Newsgroups: comp.lang.ada
Date: 2000-03-20T00:00:00+00:00
List-Id: <comp.lang.ada>

Using GNAT 3.12 on Win NT 4.0.  We have defined a record that has a length
of 214 bytes.  The type'Size attribute reports 214, but when we declare a
variable of the record type (X : Type) the size attribute X'Size reports
216.  It appears the actual variable size takes into account adjustments to
word boundaries (and of course the type'Size attribute can't do this).  Is
there a preprocessor command or pragma command that will force byte boundary
alignment so that the type size agrees with the actual size?

Thanks...
--
Bruce C. Detter III