Implement FOR/ROF statements in parser expansion #70
Conversation
This file contains 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
For now, the index label is not handled at all, but we can at least "copy+paste" statements multiple times based on the expression value
Some of the load file test cases don't rely on FOR stringization or indices, so for these test cases we can move them out of the "unimplemented" directory.
We could also substitute some other label usages this way, but it can cause off-by errors if the offset might be impacted by a FOR loop
…into ian/forrof-statement
This fixes parsing on some of the test entries
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.
Closes #39
Tasks remaining:
FORblockFORexpression using labels collected thus farFORas a label within the block when expandingStringization of index while within the block(Implement stringization of loop indices in FOR loops #72)