Purpose: describe to the implementor some of the things they must consider when using tclkit as his or her tcl base interpreter.
Intentional differences
- Tclkit includes additional extensions, which are detailed on the tclkit page
- Tclkit has fewer encodings than Tcl
- Tclkit has interactions with the VFS at times that make wrapping some Tcl extensions a challenge.
Unintentional differences (bugs?)
- glob appears to be broken inside of a tclkit. If you cd into the running tclkit, and then execute a glob on a string that does not exist anywhere on the machine, that string still is returned. PT: this appears to be a VFS bug. You can demonstrate it with non-tclkit tcl and vfs (at least with vfs::mk4).
- file permissions (and owners?) of files stored within a starkit are not (fully?) supported. Comments have been made in the past that this limitation/difference could be overcome with adequate additional code in the vfs type code.
Category Deployment | Category Tclkit