Big-endian vs little-endian

[Mike Werner <mwerner@wvu.edu>]

Now, I know that this problem has been around for a long time.  I also
am aware of the fact that it is basically a hardware implementation
based problem.  Or at least that's what I've always been told.

I recently had a project for school that involved a binary data file
that needed read using sequential IO.  As the data file was created on
the departments server and I was doing the project on my PC at home, I
ran into the endian problem.  The text string and the two enumeration
types read iin just fine - it was the two numeric fields that were
hosed.  I did manage to get around the problem by creating my own data
file to test with - fortunately the instructor told us what was in the
file.

But I got to wondering - shouldn't things like that be standardized by
now?  Or at least a way for the compiler to deal with such things?  If
such does exist, then I apologize for dragging this up and humbly
request a pointer to where to find such info.  If not ... well once I
figure out what I'm doing maybe I'll tackle that as a project some day.
-- 
Mike Werner  KA8YSD           |  "Where do you want to go today?"
ICQ# 12934898                 |  "As far from Redmond as possible!"
'91 GS500E                    |
Morgantown WV                 |

-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GU d-@ s:+ a- C++>$ UL++ P+ L+++ E W++ N++ !o w--- O- !M V-- PS+ PE+
 Y+ R+ !tv b+++(++++) DI+ D--- G e*>++ h! r++ y++++
------END GEEK CODE BLOCK------