Rebuild a display file whose program writes a format without output fields #602
Loading…
Reference in a new issue
No description provided.
Delete branch "rpg-9-d4-outfmt-20261022"
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?
Round 9 track D, D4 follow-up: the exam's real blocker. A display file whose program writes a format that has no output fields.
The held-out exam reported
1 dds blocking TODOthat was not the*SRCSTMTrefusal (#600 changed nothing in the exam). #601's fixed kinds named the family, then one more split named the refusal:display_output_formats, "the output records are not the formats that the program writes". Public reproduction:d4-out-const(CR1 has an output field, CR2 only a constant; the program writes both with EXFMT). The output block holds one record (the plan sees 2 lines for CR1); CR2 has no output specification, and the two EXFMT calls differ only in symbol ids, so the object does not say which written format owns the record.Rule: the records go to the first written formats and the member carries
TODO [placeholder] the formats of the output records(it compiles; the round trip tests the choice). More records than written formats stays blocking. The commit pair is the probes (d4-out-const,d4-out-input) and the fix.d4-out-input(a second format with only an input field) is a second gap,the place of the input lines is not proved, held in public for the next PR.Gates against the baseline of trunk before this PR (the D4-fix binary):
Exam with this binary (counts only): the display member is rebuilt (
dds_files1, blocked 0, blocking TODOs 0); the exam still fails on the host with 71 failure comments. The largest families: 29 "statement names a field of a file", 22 unresolved, 9 block part of a failed block.