A printer file without OFLIND is written in columns #667
Loading…
Reference in a new issue
No description provided.
Delete branch "rpg-l5-nooflind-20261029"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A printer file without OFLIND is written in columns
A program-described printer file without OFLIND gets an overflow record of the
compiler (
rpg_output_spec.zig: a generated record) and an overflow outputroutine after the end of the cycle, which the *OFL step calls through a
control slot. That routine stayed unproved, so the
SETON LRstatement waspartial, and columns refused the generated record.
rpg_cycle_end.zigproves the overflow output routine (roleoverflow_output): it saves the return slot of the record routines, callsthe overflow record of the compiler (its entry label is in
rpg_output_spec.Proof.overflow_entries), restores the slot, sets the cyclestate and the overflow indicator bytes, and returns through its control slot.
the compiler, the generated record has no source line, and no comment line
follows the last statement: the compiler writes its overflow record after
the last source line, and a comment there moves it (calibration E on
r6e-nooflind: the original matches, and so does it with Total as
9P 0orits D lines in symbol order; with a comment after the last O line it
differs; the emitted text matched twice).
r6e-nooflind and r6e-ho-nooflind-two are written in columns with no failure.
Gates