TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
"Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
Subject:
From:
"Anderson, Richard L" <[log in to unmask]>
Date:
Wed, 25 Mar 1998 10:57:10 -0800
Content-Type:
text/plain
MIME-Version:
1.0
Reply-To:
"Anderson, Richard L" <[log in to unmask]>
Parts/Attachments:
text/plain (22 lines)
After digging through the Ada RM and Rationale, I am still confused
about Big Endian / Little Endian.

The RM (13.5.3 paragraph 2) says that High_Order_First (known in the
vernacular as "big endian") means that the first BIT of a storage
element (bit 0) is the most significant BIT.

Other references, for example a jargon dictionary
(http://www.ufsia.ac.be/~skimo/jargon/big-endian.html), say that it has
to do with packing most significant BYTE first.

The Motorola M68332 processor packs the most significant BYTE first but
uses BIT 0 (zero) to identify the least significant BIT; hence the
confusion.  So, to use the record representation clause (RM 13.5.1) on
this processor, do I ignore the bit numbering that Motorola uses and use
the Ada bit numbering instead?

Rick Anderson

p.s.: does anyone have a web reference for the famous paper "On Holy
Wars and a Plea for Peace" by Danny Cohen?

ATOM RSS1 RSS2