Copybook: Support parsing cobol programs as copybooks #17
Labels
enhancement
New feature or request
Comments
4 tasks
bbemis017
added a commit
that referenced
this issue
Apr 16, 2023
closes #6 ### Changes - Adds an initial copybook definition interface - Adds Initial copybook parsing logic - Adds Initial copybook grammar - Supports parsing simple copybooks (still missing a lot of features) ### Context For Reviewers This is the initial copybook parser and it is able to parse simple copybooks with fields and nested groups of fields. It is very limited at the moment though so there are some more features to add later: - #14 - #16 - #15 - #17 - #19 - #20 ### Testing Build should pass ### Code Change CheckList - [X] Code runs without errors. - [X] Added/Updated tests for feature. - [X] fixed or suppressed any linting warnings. - [X] Added relevant documentation to methods, classes, markdown.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Description
Since the copybook is just a chunk of the cobol program it would be ideal to support parsing the copybook directly from the cobol program. This would mean ignoring non-relevant leading/trailing sections to the copybook in the grammar.
Use Cases
This could be useful if a copybook has not been exported from a cobol program yet. So it could save someone some time in theory, although I'm not sure if there are cases when someone would need this in practice.
Who can work this issue?
Would be open to someone picking this up
Does this feature need more scoping or discussion?
No
The text was updated successfully, but these errors were encountered: