Clear copyTokens between COPY statements to prevent copybook reuse bug #410
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.
Problem
When multiple COPY statements exist in the FILE SECTION, the tool was incorrectly expanding the same copybook (the first one encountered) for all subsequent COPY statements. This occurred because the copyTokens list in LineRepository was not being cleared between processing different COPY statements, causing tokens from the first COPY statement to persist and be reused.
Solution
Modified addAccumulatedTokensFromCopyStatementToCopyTokens() method in LineRepository.java to:
Testing
Added a new copybook FSTEST.cpy and a COPY FSTEST statement to the file section of filecopy.cbl to test this change