Next: , Previous: , Up: Imperative Language Interpreter   [Index]

5.5 Imperative Program Execution

Program may be executed from start to finish via a single function call, or step by step.

See x1f4_ever_program.

See x1f4_link_program.

See x1f4_long_program.

See x1f4_note_program.

The single call program executors do not tend to tasks such as temporaries disposal, but some of the functions allow for a method to be called back after each successfully executed instruction. The method would perform the required keeing clean tasks, together with whatever else the application has on agenda.

When executing programs step by step the execution of each instruction takes function call. Such, the application initializes program execution and than for as long as the program execution hasn’t completed and the application so desires, it executes the program instructions.

See x1f4_head_program.

See x1f4_slip_program.

See x1f4_tail_program.

Each coded expression translates to an executable instruction and control statements add each one or two extra executable instructions.

An alternative step by step execution model allows for actions prompted by program execution to be carried out outside interpreter control.

See x1f4_head_routine.

See x1f4_step_routine.

A transform of the programs is required by second step by step execution model.

See x1f4_rail_program.

The second model step by step program execution makes use of a (step by step) execution context, that has to be created before execution commences. Applications will like to dispose of such context once program execution completes.

See x1f4_near_routine.

See x1f4_side_routine.

Next: , Previous: , Up: Imperative Language Interpreter   [Index]