

(I also compile my own builds of Tcl direct from source, but then you'd expect that as I'm a developer of Tcl itself.) ActiveTcl is very convenient for when I just want to write code, and Tclkit is nice for when I'm distributing an app to other people in my organization. Myself, I use ActiveTcl and Tclkit on the same system. (The name is different for branding reasons, and they might have slightly different sets of default-packaged goodies.) They use the same packaging technology, the same file format.

ACTIVETCL VS TCL SOFTWARE
That said, the commercial tools built on top of the ActiveTcl platform (notably the ActiveState TDK) can actually produce packaged software using what they term basekits, which are effectively tclkits. There are differences in startup, library locations, etc. This is because the Tclkit distribution was designed to be used in much more embedded situations (and, originally, to fit on a floppy disk that's mostly irrelevant now that nobody has floppies any more). Tclkit tends to come with support for fewer character sets and timezones you can add these back in if you need them. Website, Major implementations ActiveTcl Androwish. This is what you'd expect from the kind of full-service Tcl distribution that it is. Tcl is a high-level, general-purpose, interpreted, dynamic programming language. Those differences:ĪctiveTcl comes with more third-party packages than Tclkit (though you can use kit-built libraries or build your own packages with both). Both are Tcl interpreters, and if you have the same version (as reported by info patchlevel) then you have the same version.
