From: dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de
Subject: Re: ASCII and BINARY files. Why?
31 Jan 1997 16:51:38 -0800
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <009AF356.2AB9D5C0.8824.cygnus.gnu-win32@ifk20.mach.uni-karlsruhe.de>
Original-To: riche AT crl DOT com
Original-CC: gnu-win32 AT cygnus DOT com, dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de
Original-Sender: owner-gnu-win32 AT cygnus DOT com

Hi, you wrote:

: Addressing the portability issue, including a "t" flag in a fopen call does
: not decrease portability in any way, as it will simply be ignored by any
: libraries which do not support it.

Is ignoring guaranteed on really all implementations, or do some produce
errors? And who assures you that some platform doesn't already use "t" with
another meaning?
I guess O_TEXT is less likely to cause an incompatibility.

FYI, I try to use the least common denominator only; what Richard Stevens'
"Advanced Programming in the UNIX Environment" doesn't explicitly mention
to work an all flavors of unix, I try to avoid.
It doesn't say anything about unimplemented type specifiers, and sure not
about fopen ignoring them. It only lists the ANSI ones.


Bye, Heribert (dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de)
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".