Date: Sun, 14 Apr 1996 15:34:51 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: DJ Delorie <dj AT delorie DOT com>
Cc: leisner AT sdsp DOT mc DOT xerox DOT com, djgpp-workers AT delorie DOT com
Subject: Re: O_BINARY/O_TEXT on open
In-Reply-To: <199604141210.IAA09430@delorie.com>
Message-Id: <Pine.SUN.3.91.960414153207.2679B-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Sun, 14 Apr 1996, DJ Delorie wrote:

> > do need to know about binary files, and include O_BINARY in the original 
> > sources where they are needed.  They can always define it to be 0 on Unix 
> > systems.
> 
> My preferred solution is to add this to the beginning of the relevent
> source files:
> 
> 	#ifndef O_BINARY
> 	#define O_BINARY 0
> 	#endif

That's what I had in mind, but I also think that every package should
already include such a definition, so that you don't have to add anything
(at least on behalf of this issue) to the original sources; *then* it
might be called ``clean''.