From:	fjh AT cs DOT mu DOT OZ DOT AU (Fergus Henderson)
Subject:	Re: ASCII and BINARY files. Why?
28 Jan 1997 08:34:28 -0800 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<199701281409.BAA31757.cygnus.gnu-win32@mundook.cs.mu.OZ.AU>
Original-To:	Paul AT chocolat DOT foobar DOT co DOT uk (Paul Shirley)
Original-Cc:	gnu-win32 AT cygnus DOT com (gnu-win32)
In-Reply-To:	<dptMxAA5aP7yEwYb@foobar.co.uk> from "Paul Shirley" at Jan 27, 97 06:40:57 pm
X-Mailer:	ELM [version 2.4 PL24]
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

Paul Shirley wrote:
> 
> AFAIK the djgpp port already handles 't' and O_TEXT modes. I had assumed
> that this came from the gnu sources ( I assumed that because who else
> would add an O_BIN flag when native DOS compilers all use O_BINARY ;)
> 
> If not, borrowing from the djgpp source should be fairly
> straightforward.

It might well be straightforward to implement 't' and O_TEXT,
but it would be a _bad idea_ to do so, because it would be a
bad idea to use those features.  Using 't' and O_TEXT would be a bad
idea even if they were implemented, because doing so would reduce
portability, rather than improving it, because they are non-standard.

-- 
Fergus Henderson <fjh AT cs DOT mu DOT oz DOT au>   |  "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh>   |  of excellence is a lethal habit"
PGP: finger fjh AT 128 DOT 250 DOT 37 DOT 3         |     -- the last words of T. S. Garp.
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -