Skip to content

det: JSON PARSE fills fixed OCCURS tables from a JSON array (Part of #7524) - #7952

Draft
squid-protocol wants to merge 1 commit into
mainfrom
churn/7524-json-parse-tables
Draft

squid-protocol wants to merge 1 commit into
mainfrom
churn/7524-json-parse-tables

Conversation

@squid-protocol

Copy link
Copy Markdown
Owner

Part of #7524 (census #7709). Checklist: partial [c:bb8e1760] -- PARSE ODO tables and floats, CONVERTING (#7949), elementary source/receiver

Class

JSON PARSE receiver tables: a JSON array into a fixed OCCURS item (elementary or group elements, nested fixed tables), translated from IBM's table format. Same mechanism as the GENERATE table slice; json_tree now allows tables for PARSE and keeps ODO and floats GENERATE-only.

Sibling gaps

Facts checked

  • Array length differing from the OCCURS count: IBM pages state nothing, so a runtime Hole, not a guess.
  • Non-array for a table: JSON-CODE 104 (type mismatch, as for scalars). Top-level array stays a Hole.
  • Register X77 updated; oracle-unbacked, no L2+ claim. No burned program uses JSON, so no case or golden moves.
  • Tests: test_det_json_parse/generate (74 pass, runtime run on JDK 17), audit_check clear, cobolrt API check holds.

Cross-repo

None. Overlaps open #7949 in gen.py and cobolrt_api.json; whichever merges second rebases.

Lessons for agents

cobolrt_api.py --promote-used only reports; a new public runtime method used by emitted code needs "visibility": "public" and the summary counts edited by hand in cobolrt_api.json.

🤖 Generated with Claude Code

…7524)

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant