A cycle program with exception output is written in columns #663
Loading…
Reference in a new issue
No description provided.
Delete branch "rpg-l2-columns-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 cycle program with exception output is written in columns
A fixed-form cycle program that writes its printer output with EXCEPT and
output specifications could not be rebuilt: a free-form source cannot hold
O-specs, so the output stayed failure comments and EXCEPT (v0.1.374) a
failure line. Such a program is now written in columns (fixed form, no
**FREE), by the new PURE modulerpg_source_columns.zig:output field names, and those that no statement names but whose initial
value proves them (
unused_mod.proved; calibration C: a missing fieldchanges the object). A packed or zoned field whose decimal positions are
not proved has 0 (
9P 0 INZ(123456)compiles to the same object as9P 2 INZ(1234.56));except LINE;compiles likeC EXCEPT LINE),SETON LRas its C line (*inlr = *oncompiles to other operations), the output specifications as O linesfrom the proved
output_specification_v1facts;columnsModetakes this path only for the proved shape: the main procedurealone, only output program-described printer files, every output record an
exception record with plain fields (no output indicators, no edit, no
overflow record of the compiler) whose write calls the line count routine.
Anything else stays free form, unchanged. Forms
emit_f_printer_v1,emit_d_standalone_v1,emit_c_seton_v1,emit_o_record_v1,emit_o_field_v1. The r6e-num test pins the text that matched its object onthe host (ROUND9 4.2g, calibration C).
Gates