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,9ae3749ddf1e6022
X-Google-Attributes: gid103376,public
From: bobduff@world.std.com (Robert A Duff)
Subject: Re: Endian and Ada
Date: 1996/04/08
Message-ID: <DpKB2C.Fyv@world.std.com>#1/1
X-Deja-AN: 146421279
references: <4kamb9$om2@flute.aix.calpoly.edu>
organization: The World Public Access UNIX, Brookline, MA
newsgroups: comp.lang.ada
Date: 1996-04-08T00:00:00+00:00
List-Id: <comp.lang.ada>

In article <4kamb9$om2@flute.aix.calpoly.edu>,
Michael Anthony Porcelli <mporcell@flute.aix.calpoly.edu> wrote:
>...One of the main problems that my
>professor likes to point out the endian problem and the fact that so much
>software is *not* endian-independant (due mainly to the widespread use of C
>and C++).  However, he is not familiar enough with Ada (nor am I) to know if
>Ada is endian-independant.

What, exactly, do you mean by "endian-independent" code?  There's a big
difference between (1) you can compile a fairly self-contained program
on both sorts of machines, and it will work, versus (2) the program is
distributed across a heterogeneous network, and wants to pass
endian-independent data from one part to another.

- Bob