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,FREEMAIL_FROM,
	INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,9ae3749ddf1e6022
X-Google-Attributes: gid103376,public
From: ljmetzger@aol.com (LJMetzger)
Subject: Re: Endian and Ada
Date: 1996/04/14
Message-ID: <4kq2lg$89@newsbf02.news.aol.com>#1/1
X-Deja-AN: 147396553
sender: root@newsbf02.news.aol.com
references: <4kamb9$om2@flute.aix.calpoly.edu>
organization: America Online, Inc. (1-800-827-6364)
newsgroups: comp.lang.ada
Date: 1996-04-14T00:00:00+00:00
List-Id: <comp.lang.ada>

On 9 Apr 1996 17:29:41 -0700 Mike Porcelli wrote:
>After reading your posts and thinking about this issue more I think that
>perhaps I've come to a better understanding of this issue and, I have
come
>up with more questions (clearer and more specific ones).  I'm wondering
if
>you all could check my understanding and let me know if it's correct or
not.
>
>1.  Endian becomes an issue when cross platform data
distribution/transfer
>is involved regardless of what programming language is used.

Any time you deal with target hardware that is not identical to the host
hardware, not only do you have to deal with the Endian problem,
but also the "which bit is lsb problem too".

e.g. I use Verdix Ada 6.2.0 (e) on a Sun (SunOs 4.1.x ) to create 
a prom image for an AMD29050 embedded processor.  The 29050
communicates with hardware (e.g. A/D converters) from different 
vendors, and on some of the hardware bit 0 is lsb, and on others
bit 0 is msb, hence the need for "Mr. Bitswap".



Lewis Metzger          LJMetzger@aol.com
Fair Lawn, NJ