Repository navigation
det: JSON PARSE takes COMP / COMP-3 / COMP-5 numeric receivers (Part of #7524, #7709) - #7920
Merged
Merged
Conversation
squid-protocol
added
the
shepherd:merge
Contributor
|
No description provided. |
Contributor
|
No description provided. |
Contributor
8 of 15 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
JSON PARSE into a group with COMP, COMP-3 / PACKED-DECIMAL or COMP-5 numbers was refused by name (
json_treeallowed packed/binary only for GENERATE). The census PARSE rows areJSON PARSE: <item> is PACKED NUMERIC. PARSE now takes those numeric usages by the same rules as DISPLAY numbers (decimal alignment, no extra decimals, no negative for an unsigned item, a value past the PICTURE digits is the exception condition). Tables stay refused for PARSE. Oracle-unbacked: register X77 updated, no L2+ claim.Class / Sibling gaps
Class: JSON PARSE / GENERATE items of a non-DISPLAY usage that
json_treerefuses by name. GENERATE was done in #7884; PARSE done here. Sibling gaps (no burned program uses JSON, so none is needed by a burned estate; census-driven): GENERATE JSON-CODE value after an exception (census GENERATE row; needs IBM's exception table), PARSE OCCURS tables, JSON-CODE / JSON-STATUS after a PARSE exception, CONVERTING, NAME OMITTED, OCCURS DEPENDING ON. SUPPRESS WHEN is #7905.Facts checked
det_port.py check: 270/270 ports unchanged. Pytest (json parse/generate, 4462, gap_prevalence, det_translate): 811 passed.audit_check.py: all clear. ruff format clean. No golden bless (det port only). Census re-survey is left to the tick (not run here).Cross-repo
None. Overlaps #7905 in
gen.py(different hunk) andcobolrt_rules.json(different line).Checklist: partial [c:9bd1fd57] -- JSON GENERATE exception JSON-CODE value (census GENERATE row), PARSE tables, JSON-CODE/JSON-STATUS after PARSE exception, CONVERTING, NAME OMITTED, OCCURS DEPENDING ON, SUPPRESS WHEN (#7905)
🤖 Generated with Claude Code