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=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,81bce7ee9133fb42 X-Google-Attributes: gid103376,public From: ncohen@watson.ibm.com (Norman H. Cohen) Subject: Re: GNAT Ada for DOS - Reading Integers Problem Date: 1996/02/20 Message-ID: <4gdivm$10f5@watnews1.watson.ibm.com>#1/1 X-Deja-AN: 140320040 distribution: world references: <4g2efj$d5d@susscsc1.rdg.ac.uk> organization: IBM T.J. Watson Research Center reply-to: ncohen@watson.ibm.com newsgroups: comp.lang.ada Date: 1996-02-20T00:00:00+00:00 List-Id: In article , dahaverk@cca.rockwell.com (Dave Haverkamp) writes: |> For ada95 look at the "Bit_Order" attribute. |> |> for T'Bit_Order use Highest_Bit_First; |> |> or |> |> for T'Bit_Order use Lowest_Bit_First; |> |> |> I'm not sure this will help in your application. But you definitely |> need to flip the bits around. No, the purpose of the 'Bit_Order attribute is not to perform big-endian/little-endian data conversion at run-time, but to assert that bit numbers in record-representation clauses should be interpreted at compile time according to either big-endian or little-endian conventions. -- Norman H. Cohen ncohen@watson.ibm.com