History

TEMU 2 supported rudimentary command line processing based on the libedit tokeniser and command line completion mechanism. The command line interpreter was line or command based and did not have any support for e.g. expressions or blocks. Scripting in tscript then was essentially producing a sequence of commands without the ability to branch or introduce functions.

As time went on more power was deemed to be needed, options such as using TCL was discarded since TCL would not be able to without major changes deal with the TEMU object system. Use cases that was deemed necessary was primarily now adding expression support (including binary and si-prefixed unit support), ability to define functions for simulating boot software and the ability to define functions supporting parameterised system model creation.

The new tscript support in TEMU 3 improves on this situation, even though parameterised system model support is primarily offloaded to the component system together with the new metaclass method support.

Operator priority based infix expressions are now supported whereever numbers were expected and commands can be defined in tscript itself to simulate boot software.