This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: ASCII and BINARY files. Why?
- To: riche at crl dot com
- Subject: Re: ASCII and BINARY files. Why?
- From: dahms at ifk20 dot mach dot uni-karlsruhe dot de
- Date: Fri, 31 Jan 1997 23:23:02 EST
- CC: gnu-win32 at cygnus dot com, dahms at ifk20 dot mach dot uni-karlsruhe dot de
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@ifk20.mach.uni-karlsruhe.de)
-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".