delorie.com/archives/browse.cgi | search |
From: | fjh AT cs DOT mu DOT OZ DOT AU (Fergus Henderson) |
Subject: | Re: ASCII and BINARY files. Why? |
2 Feb 1997 06:19:41 -0800 : | |
Approved: | cygnus DOT gnu-win32 AT cygnus DOT com |
Distribution: | cygnus |
Message-ID: | <199702020627.RAA02640.cygnus.gnu-win32@mundook.cs.mu.OZ.AU> |
Original-To: | franl AT world DOT std DOT com (Francis Litterio) |
Original-Cc: | gnu-win32 AT cygnus DOT com (gnu-win32) |
In-Reply-To: | <E4w906.MAM@world.std.com> from "Francis Litterio" at Jan 31, 97 10:27:49 pm |
X-Mailer: | ELM [version 2.4 PL24] |
Original-Sender: | owner-gnu-win32 AT cygnus DOT com |
Francis Litterio, you wrote: > > Michael Paul Smith <mike AT willingham DOT demon DOT co DOT uk> wrote: > > > The ASCII or BINARY thing is no big deal in practice. > > Then you've probably never done any of these things under UNIX: > > 1. Used cat to aggregate a partitioned gzip file: > > cat file.gz.1 file.gz.2 file.gz.3 | gunzip -c > file That one is indeed a serious problem. > 2. Used sed to change the names of symbols in an object file: > > sed 's;read;rEaD;g' < foo.o > newfoo.o You shouldn't do this anyway! It's a hack that might happen to work, if you're lucky, but you shouldn't complain if it breaks. > 3. Or even just tried to see a hex or octal dump of what's > in a file that doesn't contain text: > > od foo.gz That one could be fixed without too much difficulty by changing "od" to open the file in binary mode. Problem "1" is a much stronger argument for always using binary mode than problems "2" or "3". -- Fergus Henderson <fjh AT cs DOT mu DOT oz DOT au> | "I have always known that the pursuit WWW: <http://www.cs.mu.oz.au/~fjh> | of excellence is a lethal habit" PGP: finger fjh AT 128 DOT 250 DOT 37 DOT 3 | -- the last words of T. S. Garp. - For help on using this list, send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |