Writing An Interpreter in Go
Modified 2024-07-09
p13
- wonder if displaying error messages when parsing org-mode could prove useful
- handling the tokens as strings is bad for production, because with an
io.Readerwe can track the lexing and parsing errors
p17
- focus only on ASCII, since it's
bytebased, if unicode is important we should base all of it ofrune's.
p21
- is this what they call procedural programming?
- seeing step-by-step the effect of each function
p23
- the lexer should only turn the input into tokens, not if it makes sense and contains errors
p28
continue please...
Metadata
- Creator(s)
Thorsten Ball
ThePrimeagen
I'd like to learn how to properly parse org-mode files outside Emacs