Please note that this has also been referred to as "byte sex" as well.
Back (many years ago) I worked in a company where I ported their Business
BASIC interpreter to multiple platforms so the byte sex / endianness was
one of the first things characterized before we checked how complete the
Unix API was (there were some serious "Joe Isuzu Unix"es out there in the
mid-late 1980s).
You learn a lot about portation requirements when you deal with some of the
weirder byte orders (like the NS32032 chip). Speaking of NS32K chips,
anybody down under remember "Labtam"?
--------------------
John R. Campbell, Speaker to Machines (GNUrd) {813-356|697}-5322
Adsumo ergo raptus sum
IBM Certified: IBM AIX 4.3 System Administration, System Support
http://packrat.tampa.ibmus2.ibm.com/~soupjrc/
Backup: Toby Schmeling {813-356|697}-5233
Bernd Oppolzer
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
-online.de> cc:
Sent by: Linux on Subject: [LINUX-390] Fwd: Re: big and
little endian
390 Port
<[EMAIL PROTECTED]
IST.EDU>
08/06/2003 12:29
PM
Please respond to
Linux on 390 Port
Ok ok, I see:
big endian: the big END is stored at the BEGINNING
little endian: the little END is stored at the BEGINNING
Strange for me. I prefer the terms "normal" vs. "Intel" format :-)
Regards
Bernd
---------- Weitergeleitete Nachricht ----------
Subject: Re: big and little endian
Date: Wed, 6 Aug 2003 18:22:51 +0200
From: Bernd Oppolzer <[EMAIL PROTECTED]>
What I never understood about this: how can big ENDian be explained ?
Because, the number formats called big ENDian have the LEAST significant
byte at the END, and the little ENDians have the MOST significant byte
at the END.
Can anybody explain ?
Regards
Bernd
Am Mit, 06 Aug 2003 schrieben Sie:
> Has to do with the order of bytes and significance. Whether, for
> example, decimal 123456789 which is hex 0x75BCD15 is stored as 07 5B CD
> 15 (big endian) or 15 CD 5B 07 (little endian). Intel is little endian.
>
> ~ Daniel
>
-------------------------------------------------------
