Conversation
Author
|
Cleaned-up version of my previous request with improved comments and docstrings. |
eliben
reviewed
Oct 2, 2025
eliben
left a comment
Owner
There was a problem hiding this comment.
Thanks again, this looks pretty good!
As mentioned before, I will leave this PR open for now. I have to think more whether I want to keep interpreter.py as simple as possible, leaving the optimizations to the other methods of running bobscheme (VMs, etc)
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
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.
Got the idea from
https://www.norvig.com/lispy.html
https://www.norvig.com/lispy2.html
Create long-recursion.scm in examples:
python compile_file.py long-recursion.scm&&python run_compiled.py long-recursion.bobc==>#fpython interpret_file.py long-recursion.scmwill segfault before the patchpython interpret_file.py long-recursion.scm==>#fafter the patch