From: Chris Holmes Newsgroups: comp.os.msdos.djgpp Subject: Re: From Bytes to Int and Char Date: Sat, 14 Aug 1999 11:13:01 -0400 Organization: Georgia Institute of Technology, Atlanta GA, USA Lines: 22 Message-ID: <37B5877D.2343@surfsouth.com> References: <37B466D7 DOT 958F09E5 AT americasm01 DOT nt DOT com> <37B4DFD1 DOT 4D66 AT surfsouth DOT com> <37B57EB0 DOT 492A93AE AT unb DOT ca> NNTP-Posting-Host: r33h43.res.gatech.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: news-int.gatech.edu 934643774 11737 128.61.33.43 (14 Aug 1999 15:16:14 GMT) X-Complaints-To: usenet AT news DOT gatech DOT edu NNTP-Posting-Date: 14 Aug 1999 15:16:14 GMT X-Mailer: Mozilla 3.04Gold (Win95; I) To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Endlisnis wrote: > > > (sorry... have to say it) They aren't endians, they're native > > arrangements. Please, be PC with your PC. > > I don't know what you are talking about. The word endian means the native > order of bytes in a multibyte contiguous variable type. It was a PUN, a PUN. endian is approximately equal to Indian... native arrangement/american. Does no one appreciate horrible geek humor anymore? > I don't see how, because it's doing the exact same thing in a more obsure way. > I was trying to say that if the file was stored on a big-endian machine, then using > a little-endian like DJGPP to read the file in the way I mentioned wouldn't work. The difference is that you're telling the compiler to do the magic here, so if you compiled it on a big-endian compiler, then it should do it right. I'm just trying to save some time spent recoding. Chris