From: perfecto AT mail2 DOT nai DOT net (Perry DOT Fecteau AT Republican DOT COM)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: order of bytes written to files...
Date: Tue, 17 Mar 1998 20:49:40 GMT
Organization: Milhouse America
Lines: 22
Message-ID: <351ce1d1.501644726@news.nai.net>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 980317185848 DOT 19045N-100000 AT is>
NNTP-Posting-Host: bridgeport-usr2-22.nai.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

On Tue, 17 Mar 1998 19:01:39 +0200 (IST), Eli Zaretskii
<eliz AT is DOT elta DOT co DOT il> wrote:


>On Tue, 17 Mar 1998, Yoav Shadmi wrote:

>> If I'm not mistaken the COFF binaries (produced by DjGPP) have
>> big-endian byte ordering (i.e. the most significant byte/word comes 
>> first) in them, while most x86 binaries (Like those produced by Borland 
>> C) use the little-endian ordering.

>If I understand correctly the original message, the order of bytes in the 
>COFF binaries themselves has nothing to do with the problem.  The 
>original message described a program which, when compiled with Borland 
>and DJGPP produced different results writing integer values to a binary 
>file.  The format of the executable file has nothing to do with that.

why wouldn't it?
-- 
Dead Republican
Check out Dead Republican's anti MicroSoft song <alt.netted.out> at:
http://w3.nai.net/~perfecto/deadrep.html