This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: ASCII and BINARY files. Why?
- To: "Grant Leslie" <grantl at deerinet dot nb dot ca>
- Subject: Re: ASCII and BINARY files. Why?
- From: "Marty Leisner" <leisner at sdsp dot mc dot xerox dot com>
- Date: Fri, 31 Jan 1997 09:28:14 PST
- Cc: "GNU-WIN32" <gnu-win32 at cygnus dot com>
I didn't see my 2 cents added (I thought I posted it, I don't see it...)
In about 1984, I did enormous work on the Aztec C library to get unix
software to port painlessly. I treaded all files as binary, and
the stdio routines converted \n\r to \n. I also had a fork() which
worked -- it all worked in small model.
dj mentioned something about continued lines in preprocessors didn't
work correctly if you treated everything as binary (hmmm....maybe I
forgot to mention you also had to munge stdio).
If notepad can't handle binary files, forget about notepad...I never
saw logic in having seperate ascii and binary...Unix got it right in
saying "a file is a bytestream".
DOS configuration files need \n\r in order to work...I often administrater
a windows machine via smbfs, and use unix editors to deal with the files.
I have to remember to add the ^M
in order to work with dos... (you can always do this in a simple filter).
--
marty
leisner@sdsp.mc.xerox.com
Member of the League for Programming Freedom
-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".