5.4.2.22 End Statement
Note
This section describes the implementation of MS-VBAL §5.4.2.22 End Statement.
Syntax
| AST node | Instruction kind | Notes |
|---|---|---|
KeywordStatementNode (Token: End) |
Halt |
No resolved target. |
End lowers to the InstructionKind Halt
(RD-VBAL §3.5.2 Instruction).
Runtime Semantics
The executor dispatches the Halt instruction for End
(RD-VBAL §3.5.4 Execution).
The static execution context retains the state of immediate commands until an End command resets the
execution context to its initial state
(RD-VBAL §4.0 Program Structure and Organization).
End ends the program where it is, without unwinding the call stack: no Class_Terminate runs, for any object. The session is then reset:
- module variables and
Staticlocals return to their initial values; - every object is released;
- every open file is closed.
A program also ends this way when a run-time error reaches no handler, or when an internal error stops it, once the error is reported. An error that a handler catches unwinds the activations it leaves, and their objects terminate as they go. A program that waits at an error under a debugger has not ended, and keeps its state until it ends. A line the shell runs is a program of its own: one that ends on an error resets the session, the variables that earlier lines assigned included.
Implementation
RDCore.Runtime.Execution.ProcedureExecutordispatchesHaltinstructions.RDCore.Runtime.Execution.RuntimeProcedureInvokerleaves the activations of a program that ends as they are.RDCore.Runtime.Execution.SessionWiperesets the session.