From: scottk@utig.ig.utexas.edu (Scott Kempf) Subject: Re: ASCII and BINARY files. Why? 29 Jan 1997 13:49:01 -0800 Approved: cygnus.gnu-win32@cygnus.com Distribution: cygnus Message-ID: <199701291949.NAA04239.cygnus.gnu-win32@utig.ig.utexas.edu> Original-To: fjh@cs.mu.OZ.AU, jqb@netcom.com Original-Cc: gnu-win32@cygnus.com Original-Sender: owner-gnu-win32@cygnus.com >That approach makes interoperability between gnu-win32 software and >non-gnu-win32 software impossible. It is *not* a low suprise factor >approach, because users will be continually surprised when they try to >use gnu-win32 tools on a Windows text file, or use Windows tools on a >gnu-win32 text file. Korn's paper on UWIN says that he found that "many programs that run on Windows NT do not require the in front of each in order to work. This difference turned out to be less of a problem that (sic) we had originally expected." I don't have enough experience to evaluate this claim. Personally starting with next release I'm going to mount everything in binary. I have yet to have a program compile out of the box without a text vs. binary problem. Scott - For help on using this list, send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".