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,a883dc07df0d6bb1 X-Google-Attributes: gid103376,public From: tmoran@bix.com Subject: Re: Decoding an octet stream Date: 1999/12/02 Message-ID: #1/1 X-Deja-AN: 555877810 References: <8265dq$ecp$1@nnrp1.deja.com> X-Complaints-To: abuse@pacbell.net X-Trace: typhoon-sf.snfc21.pbi.net 944160480 206.170.24.118 (Thu, 02 Dec 1999 10:48:00 PST) Organization: SBC Internet Services NNTP-Posting-Date: Thu, 02 Dec 1999 10:48:00 PST Newsgroups: comp.lang.ada Date: 1999-12-02T00:00:00+00:00 List-Id: > Storage_Element'Size equals 8 (although the standard doesn't On a related note, last spring I had occasion to compare the sizes as given by 8*stream_element_count(TYPE) vs TYPE'size of a bunch of objects in a couple of (Windows-targeted) compilers. About 30% of the time the two size measures disagreed. The compilers did not always agree with each other, either as to when the two size measures disagreed, or what the size values were when they disagreed. These were compiler-default sizes, no rep clauses or pragmas.