Context Navigation

Changes between Version 2 and Version 3 of Ticket #393, comment 4

-              v2
+              v3
 }}}
+An abs_data structure is allocated whenever an exec_com script (or absentee job) begins execution.  That same structure is used for allocations while the script runs, unless an
+on-unit established by the script gets invoked by a signal in its CONDITION_LIST.
+An abs_data structure is allocated whenever an exec_com script (or absentee job) begins execution.  That same structure is used for allocations while the script runs, unless an on-unit established by the script gets invoked by a signal in its CONDITION_LIST.
           &on CONDITION_LIST &begin LINES &end
 To execute the LINES inside the on-unit, the absentee_listen_$execute_handler is called to establish a run-time environment in which to execute the on-unit lines.  This is the equivalent of pushing a new stack frame onto the user stack in which to run a PL/I on-unit.  The on-unit has access to the variables and labels setup by the outer script.  So when the execute_handler entry allocates a new abs_data structure, it copies all of the data from the outer-script's abs_data into the new abs_data structure to capture this outer information.  It then initializes some elements of the new structure for the on-unit's environment, while preserving data for the outer-script.