02.03.2014 Views

Tornado

Tornado

Tornado

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

5<br />

Shell<br />

Figure 5-3<br />

Components of the <strong>Tornado</strong> Shell<br />

Developer<br />

Commands<br />

Line Editing and History<br />

5<br />

TORNADO<br />

SHELL<br />

C<br />

Interpreter<br />

Tcl<br />

Interpreter<br />

WTX Tcl Back End<br />

Target<br />

Server<br />

WTX Tcl<br />

The back-end mechanism that ties together all of <strong>Tornado</strong>; the Wind River<br />

Systems Tool Exchange protocol, implemented as a set of Tcl extensions.<br />

5.8.3 Layers of Interpretation<br />

In daily use, the shell seems to be a seamless environment; but in fact, the<br />

characters you type in WindSh go through several layers of interpretation, as<br />

illustrated by Figure 5-4. First, input is examined for special editing keystrokes<br />

(described in 5.5 Shell Line Editing, p.193). Then as much interpretation as possible<br />

is done in WindSh itself. In particular, execution of any subroutine is first<br />

attempted in the shell itself; if a shell built-in (also called a primitive) with that<br />

name exists, the built-in runs without any further checking. Only when a<br />

subroutine call does not match any shell built-ins does WindSh call a target<br />

routine. See 5.2.3 Invoking Built-In Shell Routines, p.156 for more information. For a<br />

list of all WindSh primitives, see Table 5-13. .<br />

205

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!