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,ffdd4d59cbfb4caf
X-Google-Attributes: gid103376,public
From: bobduff@world.std.com (Robert A Duff)
Subject: Re: Ada 95 Numerics questions for the experts
Date: 1997/09/08
Message-ID: <EG7FIq.Ivw@world.std.com>#1/1
X-Deja-AN: 270773840
References: <dewar.872745692@merv>
 <mheaney-ya023680000209972104030001@news.ni.net> <dewar.873504953@merv>
 <mheaney-ya023680000509972116500001@news.ni.net>
Organization: The World Public Access UNIX, Brookline, MA
Newsgroups: comp.lang.ada
Date: 1997-09-08T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <mheaney-ya023680000509972116500001@news.ni.net>,
Matthew Heaney <mheaney@ni.net> wrote:
>That about explains it.  I wasn't aware that packing and component_size
>clauses were intended to be used together.  I assumed that by specifying
>the component size to be 3, that that meant the component size should be 3. 
>How naive of me!

Well, it should, but what should 'Component_Size be for an array of
3-bit components, where the implementation puts 10 of them in each word,
and leaves a gap of 2-bits at the end of each word?  (I'm assuming
32-bit words, here.)

If there's a "gap" of 1 bit between each 3-bit component, then I don't
think that should be called a "gap" at all -- we should call that
situation "4-bit components".

- Bob