summaryrefslogtreecommitdiffstats
path: root/win/tclWinFile.c
diff options
context:
space:
mode:
authorvincentdarley <vincentdarley>2003-03-18 10:51:28 (GMT)
committervincentdarley <vincentdarley>2003-03-18 10:51:28 (GMT)
commit546d6ca6ea71958e884437bf65cb7b2421590747 (patch)
tree4f3e6b8972cfe7e3df3b65f45acff6e48418048d /win/tclWinFile.c
parent7a9c4243ac433c65c5b5ac2b90bd788b15307548 (diff)
downloadtcl-546d6ca6ea71958e884437bf65cb7b2421590747.zip
tcl-546d6ca6ea71958e884437bf65cb7b2421590747.tar.gz
tcl-546d6ca6ea71958e884437bf65cb7b2421590747.tar.bz2
Fixes for three filesystem problems
Diffstat (limited to 'win/tclWinFile.c')
-rw-r--r--win/tclWinFile.c12
1 files changed, 11 insertions, 1 deletions
diff --git a/win/tclWinFile.c b/win/tclWinFile.c
index 8213e6d..f44140f 100644
--- a/win/tclWinFile.c
+++ b/win/tclWinFile.c
@@ -11,7 +11,7 @@
* See the file "license.terms" for information on usage and redistribution
* of this file, and for a DISCLAIMER OF ALL WARRANTIES.
*
- * RCS: @(#) $Id: tclWinFile.c,v 1.44 2003/02/10 12:50:32 vincentdarley Exp $
+ * RCS: @(#) $Id: tclWinFile.c,v 1.44.2.1 2003/03/18 10:51:31 vincentdarley Exp $
*/
//#define _WIN32_WINNT 0x0500
@@ -474,6 +474,16 @@ WinReadLinkDirectory(LinkDirectory)
if (0 == strncmp(copy,"\\??\\",4)) {
copy += 4;
len -= 4;
+ if (0 == strncmp(copy,"Volume{",7)) {
+ /*
+ * This is actually a mounted drive, which is in any
+ * case treated as being mounted in place, so it is
+ * in some sense a symlink to itself
+ */
+ Tcl_DStringFree(&ds);
+ Tcl_SetErrno(EINVAL);
+ return NULL;
+ }
} else if (0 == strncmp(copy,"\\\\?\\",4)) {
copy += 4;
len -= 4;
paces), and the new procedure is created in the current namespace. If \fIname\fR includes any namespace qualifiers, the procedure is created in the specified namespace. \fIArgs\fR specifies the formal arguments to the procedure. It consists of a list, possibly empty, each of whose elements specifies one argument. Each argument specifier is also a list with either one or two fields. If there is only a single field in the specifier then it is the name of the argument; if there are two fields, then the first is the argument name and the second is its default value. Arguments with default values that are followed by non-defaulted arguments become required arguments. In 8.6 this will be considered an error. .PP When \fIname\fR is invoked a local variable will be created for each of the formal arguments to the procedure; its value will be the value of corresponding argument in the invoking command or the argument's default value. Actual arguments are assigned to formal arguments strictly in order. Arguments with default values need not be specified in a procedure invocation. However, there must be enough actual arguments for all the formal arguments that do not have defaults, and there must not be any extra actual arguments. Arguments with default values that are followed by non-defaulted arguments become required arguments (in 8.6 it will be considered an error). There is one special case to permit procedures with variable numbers of arguments. If the last formal argument has the name \fBargs\fR, then a call to the procedure may contain more actual arguments than the procedure has formal arguments. In this case, all of the actual arguments starting at the one that would be assigned to \fBargs\fR are combined into a list (as if the \fBlist\fR command had been used); this combined value is assigned to the local variable \fBargs\fR. .PP When \fIbody\fR is being executed, variable names normally refer to local variables, which are created automatically when referenced and deleted when the procedure returns. One local variable is automatically created for each of the procedure's arguments. Other variables can only be accessed by invoking one of the \fBglobal\fR, \fBvariable\fR, \fBupvar\fR or \fBnamespace upvar\fR commands. The current namespace when \fIbody\fR is executed will be the namespace that the procedure's name exists in, which will be the namespace that it was created in unless it has been changed with \fBrename\fR. '\" We may change this! It makes [variable] unstable when renamed and is '\" frankly pretty crazy, but doing it right is harder than it looks. .PP The \fBproc\fR command returns an empty string. When a procedure is invoked, the procedure's return value is the value specified in a \fBreturn\fR command. If the procedure does not execute an explicit \fBreturn\fR, then its return value is the value of the last command executed in the procedure's body. If an error occurs while executing the procedure body, then the procedure-as-a-whole will return that same error. .SH EXAMPLES .PP This is a procedure that accepts arbitrarily many arguments and prints them out, one by one. .PP .CS \fBproc\fR printArguments args { foreach arg $args { puts $arg } } .CE .PP This procedure is a bit like the \fBincr\fR command, except it multiplies the contents of the named variable by the value, which defaults to \fB2\fR: .PP .CS \fBproc\fR mult {varName {multiplier 2}} { upvar 1 $varName var set var [expr {$var * $multiplier}] } .CE .SH "SEE ALSO" info(n), unknown(n) .SH KEYWORDS argument, procedure '\" Local Variables: '\" mode: nroff '\" End: