New (Feb 20 2003), tclvfs now contains a nice debugging feature for those writing tclvfs implementations:
vfs::filesystem internalerror report
proc report {} { puts stderr $::errorInfo }will do wonders! Tcl implementations are now not allowed to throw Tcl errors, only Tcl ok or posix errors.
LV When using a Starkit, one accesses files within the starkit via TclVFS. Please list here some of the differences one will see when accessing files via TclVFS rather than accessing them via a normal file system.
For instance, file ownership and permissions are not supported within many (most? all?) the VFS modules.
A user reports on comp.lang.tcl that when accessing files via VFS on Windows, the file names are case sensitive.
Vince adds that each filesystem module can choose whether to be case-sensitive or not. Most are, I believe, implemented in a case sensitive fashion. I'd be interested to know how, say vfs::ftp works when the relevant ftp site is running on a windows server (not case sensitive)...