From:	blarsen AT intervett DOT no (=?iso-8859-1?Q?Bj=F8rn_Hell_Larsen?=)
Subject:	RE: mount type, compiler barf, and sym links
21 Oct 1998 21:14:35 -0700 :
Message-ID:	<001201bdfcd6$7282af50$124b47c1.cygnus.gnu-win32@sorokin.intervett.no>
References:	<19981019121004 DOT 10517 DOT rocketmail AT send102 DOT yahoomail DOT com>
Mime-Version:	1.0
To:	<earnie_boyd AT yahoo DOT com>, <sarnold AT earthling DOT net>, <gnu-win32 AT cygnus DOT com>

Earnie writes:
> It is rather easy for the porter to fix with supplying the appropriate
> file processing mode switches to the open/fopen functions.  Treat all
> text files as text and treat all binary files as binary.  

The problem with this, again, it that creating strict divisions
between "text" and "binary" files, and "text" and "binary" tools
at times doesn't make much sense.

For instance, in the GNU-Win32 distribution, the tools "cat" and "grep"
are classified as "text tools", allowing them to handle MS files
with CRLF line separation and CTRL-Z end-of-file markers correctly.

Unfortunately, this also means that I won't be able to use the
tools the way I'm used to from my Unix days, i.e.

	cat part* | tar tzvf -

fails miserably, and 

	MATCHES=`grep -c pattern binaryfile`

won't do what I expected it to do.

I would much prefer a single global setting that I could toggle,
that would make all tools work in complete binary mode, under
the assumption that I *know* about the MS/Unix file format
differences, and would prefer to be left to deal with them
myself.



Bjorn

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -