Date: Sun, 30 Jul 2000 09:43:15 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Jim Smith <jsmith AT ethernet DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: C compiler inserts 0x0d before 0x0a?
In-Reply-To: <3983639C.16732F85@ethernet.com>
Message-ID: <Pine.SUN.3.91.1000730094250.22494E-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sat, 29 Jul 2000, Jim Smith wrote:

> > Open with O_BINARY to circumvent.
> 
> Thanks to those who replied with the above suggestion.  However, it still
> does not work.  As shown below, I simply added the O_BINARY word to the file
> open, but the extra bytes (0x0d) are still inserted into the output file.

I cannot reproduce this.  The program you posted which uses O_BINARY
works correctly on my machine, and does not add the CR characters
(0x0d) to the output.  Are you sure you are looking at the right file,
and invoking the correct program, after recompiling it?