From:	papresco AT calum DOT csclub DOT uwaterloo DOT ca (Paul Prescod)
Subject:	Re: Absolute file-path under bash (cygwin32)
16 Apr 1997 10:19:09 -0700 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<3354E347.A3E5C3EC.cygnus.gnu-win32@calum.csclub.uwaterloo.ca>
References:	<199704160854 DOT BAA13479 AT tcp DOT com>
Mime-Version:	1.0
X-Mailer:	Mozilla 4.0b3 [en] (Win95; I)
Original-To:	Hawkeye <hawkeye AT tcp DOT com>
Original-CC:	jeffdb AT netzone DOT com, gnu-win32 AT cygnus DOT com
X-Priority:	3 (Normal)
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

Hawkeye wrote:
> That could only ever work partially, at best.  Filenames aren't
> necessarily distinct words in the argument list (consider an option
> like "-I/usr/local/include"), and every word in the argument list
> shouldn't necessarily be interpeted as a cygwin filename (consider
> "echo dir /w >foo.bat").  

Either of these problems are easily fixed. How do you recognize variable
names so that they can be replaced? With a special character. I don't
know bash enough to know what character or character combination is left
over, though. Maybe $/ as in $/foo/bar.com . Do variable names ever
start with $/?

> The only "right" place to interpret filenames is in the API calls made by 
> an application.

It is already too late for that. We can't fix all of the Windows
software in the world, and we can't fix all of the Unix source code in
the world. We must either manually convert pathnames forever or we must
have a way of letting the computer differentiate them. I prefer the
latter.

 Paul Prescod


-
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 -