Making a Python interpreter in 1024 bytes
austinhenley.com
Making a Python interpreter in 1024 bytes
1–10 of 120 posts
Re: Making a Python interpreter in 1024 bytes
#2A lot of criticism of python often mentions the whitespace as lexical scope tokens, and that criticism is usually posited by users of the language.
As implementer of an interpreter, did you feel that whitespace for lexical scoping made the job of writing the lexer significantly more complex?
Re: Making a Python interpreter in 1024 bytes
#3A lot of criticism of python often mentions the whitespace as lexical scope tokens, and that criticism is usually posited by users of the language. As implementer of an interpreter, did you feel that whitespace for lexical scoping made the job of writing the lexer significantly more complex?
And, there are multiple white space symbols!
is different than
So you also have to track the actual sequence of counts of white space used for each level, rather than just a simple count.
Re: Making a Python interpreter in 1024 bytes
#4the blog post is pretty well-written! loved how he wrote about the the code-golfing part.
Re: Making a Python interpreter in 1024 bytes
#5For those who actually need something like this in production, there is Snek: https://sneklang.org/> “Snek is a tiny embeddable language targeting processors with only a few kB of flash and ram.”
Re: Making a Python interpreter in 1024 bytes
#6A lot of criticism of python often mentions the whitespace as lexical scope tokens, and that criticism is usually posited by users of the language. As implementer of an interpreter, did you feel that whitespace for lexical scoping made the job of writing the lexer significantly more complex?
And, there are multiple white space symbols! is different than So you also have to track the actual sequence of counts of white space used for each level, rather than just a simple count.
Or you just forbid mixing spaces and tabs in the same indentation sequence, the way most whitespace-sensitive languages seem to end up doing. Or you make a slightly more reasonable rule: spaces may follow tabs, but no tabs may follow a space. That's at least unambiguous.
Re: Making a Python interpreter in 1024 bytes
#7Good use of free will and well-written. Very nice walkthrough austin!
Re: Making a Python interpreter in 1024 bytes
#8I was very disappointed that this is “interpreting” some tiny made up language.
This is not Python, or even within three orders of magnitude of Python.
Re: Making a Python interpreter in 1024 bytes
#9A lot of criticism of python often mentions the whitespace as lexical scope tokens, and that criticism is usually posited by users of the language. As implementer of an interpreter, did you feel that whitespace for lexical scoping made the job of writing the lexer significantly more complex?
And, there are multiple white space symbols! is different than So you also have to track the actual sequence of counts of white space used for each level, rather than just a simple count.
> is different than
in my view, both are the same, both `is` (or ===) an IndentationError raise
Re: Making a Python interpreter in 1024 bytes
#10This seems to be in the same spirit as Justine Tunney's SectorLISP. Very cool.