Re: file command bug on windows
- From: Óscar Fuentes <ofv@xxxxxxxxxx>
- Date: Mon, 06 Apr 2009 00:08:45 +0200
Don Porter <dgporter@xxxxxxxxxxx> writes:
Well, it may be documented, it may be useful, but it is broken. A
leading tilde is just another symbol on Windows, and it is not different
from an 'A'. If tcl treats it on a specific way, Tcl is broken.
You should realize that tilde is also 'just another symbol' on UNIX as
well. It is just that *tradionally* it is a shorthand (in sh, csh,
bash, etc.) for a users home directory as well, and this shorthand
usage is also used in tclsh/wish, as well as other. The 'trick' of
preceding a leading tilde with a directory spec (eg "./") to suppress
the home directory substitution works for UNIX as well. Under UNIX
"./~foo" is a ligit filename and is a filename that starts with the
literal character '~'. A bit awkward do deal with from a command
shell, but not any worse than a filename starting with a dash.
I have news for you: Windows is not Unix. ...
The time for this argument was ~1996 when Tcl was first ported
to Windows.
Think of it as if fixing a long-standing bug. At least for Windows.
[snip]
--
Oscar
.
- Follow-Ups:
- Re: file command bug on windows
- From: Gerald W. Lester
- Re: file command bug on windows
- References:
- Re: file command bug on windows
- From: solar
- Re: file command bug on windows
- From: Gerald W. Lester
- Re: file command bug on windows
- From: solar
- Re: file command bug on windows
- From: Mark Janssen
- Re: file command bug on windows
- From: Óscar Fuentes
- Re: file command bug on windows
- From: Robert Heller
- Re: file command bug on windows
- From: Óscar Fuentes
- Re: file command bug on windows
- From: Don Porter
- Re: file command bug on windows
- Prev by Date: Re: file command bug on windows
- Next by Date: Re: file command bug on windows
- Previous by thread: Re: file command bug on windows
- Next by thread: Re: file command bug on windows
- Index(es):
Relevant Pages
|