 idiosyncrasies from command to command are usually driven by historical reasons, but I'm just trying to make a point.)
An alternative to little languages is sometimes to have a great many parameters for the programmer to set. Tcl/Tk features with that kind of interface include:
Some problems lend themselves towards one approach, some rather to the other. As a matter of Tcl Advocacy
it is however interesting to observe that most languages other than Tcl have a syntactical rigidity that makes it difficult to take the little language route.
Some little languages that are not part of the Tcl/Tk core are:
The term "little language" is also used in a book by Kernighan and Pike: The practice of programming. That is a book I quite enjoyed reading and it uses examples in Awk
for other little languages.
This begs the question of what the semantics of Tcl would be without any little languages, which implies being without any commands. To this end, tcl-null
discusses Tcl stripped of all commands, as a beautiful but useless language - the process of adding back a minimal subset of Tcl built-in commands is launched as a game for the obsessive.
See Also edit
- Little Languages, C2 wiki