diff options
Diffstat (limited to 'doc/file.n')
| -rw-r--r-- | doc/file.n | 38 |
1 files changed, 18 insertions, 20 deletions
@@ -5,7 +5,7 @@ '\" See the file "license.terms" for information on usage and redistribution '\" of this file, and for a DISCLAIMER OF ALL WARRANTIES. '\" -'\" RCS: @(#) $Id: file.n,v 1.15 2002/05/02 20:15:20 vincentdarley Exp $ +'\" RCS: @(#) $Id: file.n,v 1.16 2002/05/08 04:36:54 davygrvy Exp $ '\" .so man.macros .TH file n 8.3 Tcl "Tcl Built-In Commands" @@ -226,21 +226,19 @@ under Windows or AppleScript on the Macintosh. .TP \fBfile normalize \fIname\fR . -Returns a unique normalised path representation for the file-system -object (file, directory, link, etc), whose string value can be used as -a unique identifier for it. A normalized path is one which has all -'../', './' removed. Also it is one which is in the ``standard'' -format for the native platform. On MacOS, Unix, this means the -segments leading up to the path must be free of symbolic links/aliases -(but the very last path component may be a symbolic link), and on -Windows it also means means we want the long form (when running Win -NT/2000/XP) or the short form (when running Win 95/98) with that form's -case-dependence (which gives us a unique, case-dependent path). The -one exception concerning the last link in the path is necessary, -because Tcl or the user may wish to operate on the actual symbolic link -itself (for example 'file delete', 'file rename', 'file copy' are -defined to operate on symbolic links, not on the things that they point -to). +Returns a unique normalised path representation for the file-system +object (file, directory, link, etc), whose string value can be used as +a unique identifier for it. A normalized path is one which has all '../', './' +removed. Also it is one which is in the ``standard'' format for the native +platform. On MacOS, Unix, this means the segments leading up to the path +must be free of symbolic links/aliases (but the very last path component +may be a symbolic link), and on Windows it also means means we want the +long form (when running Win NT/2000/XP) or the short form (when running Win +95/98) with that form's case-dependence (which gives us a unique, +case-dependent path). The one exception concerning the last link in the +path is necessary, because Tcl or the user may wish to operate on the +actual symbolic link itself (for example 'file delete', 'file rename', 'file copy' +are defined to operate on symbolic links, not on the things that they point to). .PP Note that this means normalized paths are different on old Windows operating systems (95/98) and new Windows operating systems @@ -355,10 +353,10 @@ the second element may be null. For example the native files have a first element 'native', and a second element which is a platform-specific type name for the file's system (e.g. 'NTFS', 'FAT', etc), or possibly the empty string if no further information is available or if this -is not implemented. A generic virtual file system might return the list -'vfs ftp' to represent a file on a remote ftp site mounted as a virtual -filesystem through an extension called 'vfs'. If the file does not -belong to any filesystem, an error is generated. +is not implemented. A generic virtual file system might return the +list 'vfs ftp' to represent a file on a remote ftp site mounted as a +virtual filesystem through an extension called 'vfs'. If the file does +not belong to any filesystem, an error is generated. .TP \fBfile tail \fIname\fR . |