Share environment code between exe and sh backend (WIP) #98
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
laurenthuberdeau
force-pushed
the
laurent/unify-env-code
branch
5 times, most recently
from
4ae6fad
to
cde112e
Compare
It will be added later but this time using `const` type qualifier instead of analyzing the code.
Local scoping rules are still to be implemented, but I want to make more changes so splitting this work in smaller commits to make reviewing easier.
laurenthuberdeau
force-pushed
the
laurent/unify-env-code
branch
from
cde112e
to
b7f7da2
Compare
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.
Context
As we work towards compiling TCC, we'll be making changes to how variables and types are scoped. To make it possible to share those new features between the exe and sh backends, they first need to share their environment code.