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,72340e997bfd5289
X-Google-Attributes: gid103376,public
From: "Matthew Heaney" <matthew_heaney@acm.org>
Subject: Re: array size
Date: 1999/12/12
Message-ID: <38532e6d_2@news1.prserv.net>#1/1
X-Deja-AN: 559600339
Content-transfer-encoding: 7bit
References: <101219991605504828%hopperj@macconnect.com>
 <3852831a.0@news.pacifier.com> <111219991626405236%hopperj@macconnect.com>
 <38532c6a.0@news.pacifier.com>
Content-Type: text/plain; charset="US-ASCII"
X-Complaints-To: abuse@prserv.net
X-Trace: 12 Dec 1999 05:11:09 GMT, 32.101.8.154
Organization: Global Network Services - Remote Access Mail & News Services
Mime-version: 1.0
Newsgroups: comp.lang.ada
Date: 1999-12-12T00:00:00+00:00
List-Id: <comp.lang.ada>

In article <38532c6a.0@news.pacifier.com> , "DuckE" 
<nospam_steved@pacifier.com> wrote:

> BTW: When I tested your code on NT I was guessing that I would need some
> sort of component_size representation clause in the array declaration (as
> has been described in the 3 bit array thread).  I was actually suprised at
> my result.

In general, if you want to completely specify the representation of the
type, you should specify everything, including the Component_Size.

Use pragma Pack when you want to optimize for space, and when you don't
care about exact representation.