fix to bug 553320

1 files changed, 15 insertions, 10 deletions

diff --git a/doc/FileSystem.3 b/doc/FileSystem.3
index 413c119..01a3585 100644
--- a/doc/FileSystem.3
+++ b/doc/FileSystem.3
@@ -4,7 +4,7 @@
 '\" See the file "license.terms" for information on usage and redistribution
 '\" of this file, and for a DISCLAIMER OF ALL WARRANTIES.
 '\" 
-'\" RCS: @(#) $Id: FileSystem.3,v 1.22 2002/05/02 20:15:20 vincentdarley Exp $
+'\" RCS: @(#) $Id: FileSystem.3,v 1.23 2002/05/07 18:03:04 vincentdarley Exp $
 '\" 
 .so man.macros
 .TH Filesystem 3 8.4 Tcl "Tcl Library Procedures"
@@ -241,15 +241,20 @@ filesystem which has been registered (through
 media or access methods.  This means that all of these functions (and
 therefore the corresponding \fBfile\fR, \fBglob\fR, \fBpwd\fR, \fBcd\fR,
 \fBopen\fR, etc.  Tcl commands) may be operate on 'files' which are not
-native files in the native filesystem.  If appropriate vfs's have been
-registered, the 'files' may, to give two examples, be remote (e.g.
-situated on a remote ftp server) or archived (e.g. lying inside a .zip
-archive).  Such registered filesystems provide a lookup table of
-functions to implement all or some of the functionality listed here.
-Finally, the \fBTcl_FSStat\fR and \fBTcl_FSLstat\fR calls abstract
-away from what the 'struct stat' buffer buffer is actually declared to
-be, allowing the same code to be used both on systems with and systems
-without support for files larger than 2GB in size.
+native files in the native filesystem.  This also means that any Tcl
+extension which accesses the filesystem through this API is
+automatically 'virtual filesystem aware'.  Of course, if an extension
+accesses the native filesystem directly (through platform-specific
+APIs, for example), then Tcl cannot intercept such calls.  
+.PP
+If appropriate vfs's have been registered, the 'files' may, to give two
+examples, be remote (e.g. situated on a remote ftp server) or archived
+(e.g. lying inside a .zip archive).  Such registered filesystems provide
+a lookup table of functions to implement all or some of the functionality
+listed here.  Finally, the \fBTcl_FSStat\fR and \fBTcl_FSLstat\fR calls
+abstract away from what the 'struct stat' buffer buffer is actually
+declared to be, allowing the same code to be used both on systems with
+and systems without support for files larger than 2GB in size.
 .PP
 The \fBTcl_FS...\fR are objectified and may cache internal
 representations and other path-related strings (e.g. the current