Conversation
Owner
Author
|
Hello world example: Default error message: |
Owner
Author
|
Improved error message: |
Owner
Author
|
The hello world example has been taken from Wikipedia and the 400 bytes quine from Daniel B Cristofani. TODO: Add comment support for example attribution |
Owner
Author
|
Merged
Owner
Author
|
Why is the X an unexpected token? Shouldn't all text just be ignored? |
Owner
Author
All tokens that are not instructions are now ignored but that was not the case with the example parser I started with from the crate's repo. |
Merged
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.

I'm working on MOROS Shell 2.0 and I'll need a parser to handle the new language features. I don't like how hard it is with the
nomcrate to display good error messages with context for MOROS Lisp (which complicate a lot writing big programs inside MOROS), so I've been looking into thechumskycrate instead. That's the only issue I have withnombecause it's a really good library otherwise.When I learned how to use
nom4 years ago I added a smallcalctool with a simple grammar (#263), so I'm now using the Brainfuck interpreter from the examples of thechumskycrate with the goal to extend it a bit and see if I like the crate.I'm not sur if I'll merge this because I'm more interested in writing my own Brainfuck interpreter in MOROS Lisp, but I'm very interested in having a Brainfuck interpreter! Maybe I'll have both to compare the performance, like I did with the undocumented
picommand (that I just remembered now).