Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!aramis.rutgers.edu!topaz.rutgers.edu!busboys.rutgers.edu!gaynor
From: gaynor@busboys.rutgers.edu (Silver)
Newsgroups: comp.lang.c
Subject: Re: byte order and bit order
Message-ID: <Jul.2.05.10.42.1990.1046@busboys.rutgers.edu>
Date: 2 Jul 90 09:10:46 GMT
References: <1990Jun19.221359.7399@ecn.purdue.edu> <1990Jun20.182745.3730@csrd.uiuc.edu> <2709@tmiuv0.uucp>
Distribution: na
Organization: Rutgers Univ., New Brunswick, N.J.
Lines: 8

This is where the internet's `network ordering' conventions really come in
handy.  Non-local i/o is assumed to be with a device that formats this
low-level stuff in the `standard' network format.  Data read from such a source
must be converted to conform to local conventions with a function (or macro, as
the case may be); data so written must be converted to network formats the same
way.

Just my two bits, [Ag] gaynor@topaz.rutgers.edu