-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PPJ support and pre-scan namespace resolution #27
Conversation
`-o` was going to `--optimize` instead of `--output`
Backend compiler still uses strings
os independence!
We probably want to remove the cwd from the default imports if we’re in modern mode; there’s no longer a need for it and it can lead to unexpected behavior. |
Anyone still alive? /s |
hey @nikitalita, this PR is marked as draft but @Orvid has approved it. Does that mean that this code is all good to merge? I really like this feature and I'd like to use your fork, but I do want to make sure that I won't run into any catastrophic issues on the way. |
Thank you so much! |
this might solve the build issue: |
This implements PPJ support and pre-scanning non-PCompiler/PPJ input files for namespace resolution.
So basically, we have two different namespace resolution schemes:
"""classic""" mode:
Modern mode:
We probably want to do a refactor on the compiler nodes to have it split into two separate things; a Read/pre-parse node and everything else, since the input params for the nodes get modified after the namespace has been resolved