Introduce a **LISP INTERPRETER**, for our compiler.#173
Merged
Conversation
Once complete this will close #170 by implementing a lisp interpreter within our own language: * Compile inception.lisp -> inception * Then run programs which are /interpreted/ using it. We support string/int/float/symbol/defun/lambda and the only real issue with it is that the standard-library is mostly absent.
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.
Once complete this will close #170 by implementing a lisp interpreter within our own language:
We support string/int/float/symbol/defun/lambda and the only real issue with it is that the standard-library is mostly absent.