Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!brutus.cs.uiuc.edu!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!phil
From: phil@ux1.cso.uiuc.edu
Newsgroups: comp.lang.c
Subject: Re: RISC Machine Data Structure Word Al
Message-ID: <6200024@ux1.cso.uiuc.edu>
Date: 2 Feb 90 01:39:58 GMT
References: <111@melpar.UUCP>
Lines: 11
Nf-ID: #R:melpar.UUCP:111:ux1.cso.uiuc.edu:6200024:000:487
Nf-From: ux1.cso.uiuc.edu!phil    Feb  1 14:42:00 1990


Another problem you can encounter when dealing with data structure formats
imposed by hardware, particularly external hardware, is the byte order.
An example is handling TCP and IP headers.  The exact data structure is
defined very specifically, but making code that can deal with it AND be
portable across big and little endian machines requires a lot of care.
Such portable code may not be the most optimal depending on how it is
done.

--Phil Howard, KA9WGN--
<phil@ux1.cso.uiuc.edu>