Xref: utzoo comp.lang.c++:13221 comp.lang.c:38968
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!uunet!stanford.edu!shap@shasta.Stanford.EDU
From: shap@shasta.Stanford.EDU (shap)
Newsgroups: comp.lang.c++,comp.lang.c
Subject: Re: 64 bit architectures and C/C++
Message-ID: <181@shasta.Stanford.EDU>
Date: 3 May 91 03:33:58 GMT
References: <168@shasta.Stanford.EDU> <13229@goofy.Apple.COM> <1991May01.172042.5214@buster.stafford.tx.us>
Organization: Stanford University Computer Systems Laboratory
Lines: 11

In article <1991May01.172042.5214@buster.stafford.tx.us> rli@buster.stafford.tx.us writes:
>turk@Apple.COM (Ken "Turk" Turkowski) writes:
>
>>It is necessary to have 8, 16, and 32-bit data types, in order to be able
>>to read data from files.  I would suggest NOT specifying a size for the int
>>data type; this is supposed to be the most efficient integral data type
>>for a particular machine and compiler.
>
>You assume a lot about the data in the file.  Is it stored in a specific
>processor format (ala Intel vs Motorolla)?  My experience has been that
>binary data is not portable anyway.