Subject: RE: ASCII and BINARY files. Why?
From: [email-masked] (Fran Litterio)

29 Jan 1997 13:14:03 -0800
Approved: [email-masked]
Distribution: cygnus
Message-ID: <c=US%a=_%p=Amulet._Inc.%l=[email-masked]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Original-To: "[email-masked]'" <[email-masked]>
Original-Cc: "'Fergus Henderson'" <[email-masked]>
X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.994.63
Original-Sender: [email-masked]

Fergus Henderson wrote:

>Jim Balter, you wrote:

>> and/or the library
>> could allow a special name form such as dos:filename that causes it to
>> open the file in "text" mode.
>
>[...] (b) that still doesn't solve the problem of using Windows tools on
>gnu-win32 text files.

What problem is that?  Windows tools work fine on gnu-win32 text files
(i.e., text files without any ^M's) -- at least every Windows tool I
have tried.  David Korn's UWIN project has decided to open all files in
binary mode all the time precisely because so few (if any) Windows apps
care whether a text file contains ^M characters or not.
--
Francis Litterio
[email-masked]
http://world.std.com/~franl/

-
For help on using this list, send a message to
"[email-masked]" with one line of text: "help".