Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!sri-unix!hplabs!tektronix!uw-beaver!ubc-vision!alberta!bjorn
From: bjorn@alberta.UUCP (Bjorn R. Bjornsson)
Newsgroups: comp.sys.m68k
Subject: Re: Intel vs Motorola Byte ordering
Message-ID: <138@pembina.alberta.UUCP>
Date: Thu, 27-Nov-86 01:39:14 EST
Article-I.D.: pembina.138
Posted: Thu Nov 27 01:39:14 1986
Date-Received: Sun, 30-Nov-86 19:39:19 EST
References: <1509@ihlpl.UUCP> <1335@hoptoad.uucp>
Organization: U. of Alberta, Edmonton, AB
Lines: 21

In article <1335@hoptoad.uucp>, gnu@hoptoad.uucp (John Gilmore) writes:
> If enough people are apathetic (e.g. don't complain), I will post a
> great piece, "On Holy Wars and a Plea for Peace", which is the best
> description of byte ordering problems I've ever seen.  ......

If I recall correctly, the biggest problem with this paper was
it's bias, Cohen expresses a definite preference (not in so many
words, but it shines through), and leaves out some, good arguments
for the little endian side.  I'm not unbiased either, but I certainly
don't pretend to be.  I'll elucidate, if this discussion gets of the
ground again.

Then again, I can work quite comfortably with either byte ordering,
and do, on Suns and Vaxen, many times with applications that are
sensitive to the particular order.  When it's an issue, big endian
usually makes things a little bit more interesting, if you have
trouble disposing of your free time that is.


				Bjorn R. Bjornsson
				alberta!bjorn