delorie.com/archives/browse.cgi | search |
Date: | Sun, 14 Apr 1996 08:10:19 -0400 |
From: | dj (DJ Delorie) |
Message-Id: | <199604141210.IAA09430@delorie.com> |
To: | eliz AT is DOT elta DOT co DOT il |
CC: | leisner AT sdsp DOT mc DOT xerox DOT com, djgpp-workers AT delorie DOT com |
In-reply-to: | <Pine.SUN.3.91.960414082333.1640I-100000@is> (message from Eli Zaretskii on Sun, 14 Apr 1996 08:31:29 +0200 (IST)) |
Subject: | Re: O_BINARY/O_TEXT on open |
> I think the cleanest way is to get FSF (or at least the individuals who > maintain the different packages) to finally recognize that some systems > 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 Then just use O_BINARY where needed. You can put O_TEXT in there if you need to, but I always leave the default as text.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |