Lines of xvfs-core.c from check-in 32b55a907b that are changed by the sequence of edits moving toward check-in e5b6962adf:

                         1: #include <xvfs-core.h>
                         2: #include <tcl.h>
                         3: 
                         4: /*
                         5:  * There are three (3) modes of operation for Xvfs_Register:
                         6:  *    1. standalone -- We register our own Tcl_Filesystem
                         7:  *                     and handle requests under `//xvfs:/<fsName>`
                         8:  *    2. client -- A single Tcl_Filesystem is registered for the
                         9:  *                 interp to handle requests under `//xvfs:/` which
                        10:  *                 then dispatches to the appropriate registered
                        11:  *                 handler
                        12:  *    3. flexible -- Attempts to find a core Xvfs instance for the
                        13:  *                   process at runtime, if found do #2, otherwise
                        14:  *                   fallback to #1
                        15:  *
                        16:  */
32b55a907b 2019-05-02   17: static int Xvfs_Register_Standalone(Tcl_Interp *interp, const char *fsName, int protocolVersion, xvfs_proc_getChildren_t getChildrenProc, xvfs_proc_getData_t getDataProc) {
32b55a907b 2019-05-02   18: 	Tcl_SetResult(interp, "Not implemented", NULL);
32b55a907b 2019-05-02   19: 	return(TCL_ERROR);
32b55a907b 2019-05-02   20: }
32b55a907b 2019-05-02   21: 
32b55a907b 2019-05-02   22: int Xvfs_Register(Tcl_Interp *interp, const char *fsName, int protocolVersion, xvfs_proc_getChildren_t getChildrenProc, xvfs_proc_getData_t getDataProc) {
32b55a907b 2019-05-02   23: 	return(Xvfs_Register_Standalone(interp, fsName, protocolVersion, getChildrenProc, getDataProc));
                        24: }