Tcl
termnetworking
Tool Command Language: a scripting language designed in 1988 to be embedded inside other people's programs, so that each tool would not invent a command language of its own.
Ousterhout built it out of frustration that every tool he encountered had grown its own half-designed scripting language, and he shipped it as a C library precisely so an application could gain a scripting layer without recompiling. That design decision determined where it ended up: Tcl is rarely the language you choose for a project and frequently the language you find inside a product you bought. It is the scripting layer of network test equipment, the language F5 iRules are written in, and, through Don Libes's Expect extension of 1990, the way a generation automated devices that only offered a terminal. Anyone who learned it to drive one vendor's tool has usually found it waiting inside another one years later.
Also known as: tool command language, tcl/tk, ousterhout
Sources
- Tcl designed by John Ousterhout at Berkeley, first appearing in 1988, born out of frustration with programmers devising their own languages for extending electronic design automation software; designed as a C library so an application could embed a lightweight interpreter and be extended by scripts without recompiling
- Ousterhout's own account: the idea came on sabbatical at DEC's Western Research Laboratory in autumn 1987, implementation began at Berkeley in spring 1988, and the first external releases were in 1989