Context Navigation

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

v3	v4
87	87	However, now LINES from the &on-unit being executed are read and invoked. These do cause allocations in the 800 word abs_data.work_area, which sometimes require adding a new component area to the extensible area. Such addition is recorded in the extend_block of the 800 word abs_data.work_area, and linked to any prior components in the extensible area. As yet, no data has been lost.
88	88
89		When execution of the &on-unit LINES finishes, absentee_listen_ jumps to the EGRESS label, which invokes the finish_up subroutine. This routine has the job of ~~disposing of~~ the new abs_data structure, and restoring use of the prior abs_data structure. According to the comment highlighted above, contents of the 800 word first component of the abs_data.work_area is supposed to be copied back into the outer-script's work_area. But finish_up frees the new abs_data structure WITHOUT copying it back.
	89	When execution of the &on-unit LINES finishes, absentee_listen_ jumps to the EGRESS label, which invokes the finish_up subroutine. This routine has the job of freeing the new abs_data structure, and restoring use of the prior abs_data structure. According to the comment highlighted above, contents of the 800 word first component of the abs_data.work_area is supposed to be copied back into the outer-script's work_area. But finish_up frees the new abs_data structure WITHOUT copying it back.
90	90
91	91	{{{