<> ** Attributes ** '''What''': Tcl '''Where''': [http://tcl.tk%|%tcl.tk%|%] '''Where''': [http://tcl.sf.net/%|%tcl.sf.net%|%] '''Description''': An embeddable dynamic language interpreter. The sample "[tclsh]" is frequently used as a shell interpreter. Currently at version 8.6.0. '''Updated''': 2012-11-29 '''Contact''': See web site ** Description ** Tcl, is an acronym for '''Tool Command Language'''. The preferred pronunciaiton is as its individual letters. In the past, the most popular pronunciation was as a homophone for "tickle". The suggested spelling is with an uppercase "T" and "cl". For many people, their first acquaintance with Tcl is as a component of another software program. Examples include [Expect], [Cisco IOS] * Out of the box, '''[tclsh]''' is a stand alone interpreter build from the tcl source code distribution * '''[wish]''' is a tcl interpreter with the Tk [extension] pre-loaded. It is created when building [Tk]. * [tclkit] is a all-in-one-file combination of Tcl, Tk, [Metakit], [Itcl], [tclvfs] and a few other extensions. It is used for code in [starkit] format. * '''[expect]''' is a tcl interpreter with the expect extension pre-loaded. It is created when building expect. * A command called '''tcl''' (as well as '''wishx''') used to be built and installed as a part of building and installing the [Tclx] extension. * '''itclsh''' is a tclsh pre-extended with [Itcl]. * '''tixwish''' is built and installed as a part of the [Tix] build process * '''bltsh''' and '''bltwish''' are built and installed as a part of the [BLT] build process. * '''tcldomsh''' is built and installed as a part of the [TclDOM] build process * '''xotclsh''' and '''xowish''' are built and installed as a part of the [XOTcl] build process. As of Tcl 8.4, the only interpreters that you really need to think about are '''tclsh''', '''tclkit''', and (on some platforms) '''wish''', as Tcl provides the ability to dynamically load any of the other extensions during runtime. In fact, many of the extensions have been dropping the building and installing of custom executables due to this. [Tcl Commands] documents all the Tcl commands available in the [core] [distribution]. [Tcl C API] documents all the public Tcl C calls that a C programmer should consider ''safe'' to use. Tcl also comes with several [package]s. For instance, the [http] package, [dde], [msgcat], [platform], [registry], [tcltest], the deprecated [optparse] package, as well as others [[please fill them in here]]. ** [Tcl Advocacy%|%Why Tcl%|%] ** see [Tcl Advocacy%|%Why Tcl%|%] ** See Also ** [http://purl.org/net/tcl-faq/%|%Tcl FAQ%|%]: (desperately needs updating) [http://en.wikipedia.org/wiki/Tcl%|%Wikipidea, English)%|%]: [http://de.wikipedia.org/wiki/Tcl%|%Wikipidia, GermanTcl%|%]: [64-bit computing]: [Arts and crafts of Tcl-Tk programming]: [The way tcl works]: [Tcl Command Evaluation: Layer by Layer]: ** Supported Platforms ** See [http://www.tcl.tk/software/tcltk/platforms.html%|%this page%|%] for details about platforms known to support Tcl and [Tk]. ** [Getting Tcl/Tk] ** See [Getting Tcl/Tk] ** [Installing Tcl] ** See [Installing tcl] ** [Documentation] ** See [Documentation] ** [The Tcl Core%|%Development of Tcl] ** ** [Learning Tcl] ** See [Learning Tcl] ** [syntax] ** ** [Tcl Syntax] ** see [Tcl Syntax] ** [Tcl Commands%|%Commands%|%] ** see [Tcl Commands] ** Programs ** [A Tcl repository]: [Extensions for Tcl and Tk]: <> Language | Tcl Implementations