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,8201deea80f1752a X-Google-Attributes: gid103376,public From: Robert A Duff Subject: Re: 3-bit array ... Date: 1999/12/07 Message-ID: #1/1 X-Deja-AN: 557760448 Sender: bobduff@world.std.com (Robert A Duff) References: <382386fe.85782690@news.uswest.net> <384728ff.588431360@news.uswest.net> <3847EF64.EBD41169@callnetuk.com> <82hlkq$968$1@nnrp1.deja.com> Organization: The World Public Access UNIX, Brookline, MA Newsgroups: comp.lang.ada Date: 1999-12-07T00:00:00+00:00 List-Id: Robert Dewar writes: > I must say I wonder if the GNAT (and now Averstar) decision is > the right one. It would have been cleaner to say Pack always > means 4, and you use a component size clause if you want 3. It would be a Good Thing if all compilers did the same thing for sort of thing. > Bob, how far did Averstar go, did you just do 3 bits? In GNAt > we close pack all sizes up to 64. (e.g. an array of Natural > gets packed to 31, which can be quite a surprise, although the > pragma Pack in this case is junk!) I had better let Tucker answer that. I've already given one piece of misinformation in my original post. I didn't do the work myself, so I don't know the details. - Bob