Introduce translation phase#101
Merged
Merged
Conversation
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
1 participant
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.
This takes the parser's internal Abstract Syntax Tree and lowers it to an Intermediate Representation with symbols resolved and a series of operations to be evaluated.
This happens in a new
translationphase after theparsingphase to the compiler. The technique check command is now augmented with an--untiloption that if specified stops the compiler after reaching and completing that phase.The Intermediate Representation deliberately uses type names that are different than those used by the surface language's Abstract Syntax Tree representation. So a Technique language::Procedure becomes program::Subroutine and so on.
Reorganized the known-good and known-bad test samples by phase.