Making a Python interpreter in 1024 bytes

(austinhenley.com)

48 points | by azhenley 1 hour ago

7 comments

  • anitil 4 minutes ago
    This is really cool! It's so fun to see what you can achieve and what's optional. I have seen the 'single character variable' limitation in some other minilangs before, but using the source itself as the target of function calls and loops is new to me. It does make a lot of sense but I wouldn't have thought of that.
  • teddyh 1 hour ago
    For 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.
  • tempodox 35 minutes ago
    This seems to be in the same spirit as Justine Tunney's SectorLISP. Very cool.

    https://justine.lol/sectorlisp/

  • TZubiri 1 hour ago
    A 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?

    • nomel 1 hour ago
      And, there are multiple white space symbols!

      <space><space><tab><space>

      is different than

      <space><tab><space><space>

      So you also have to track the actual sequence of counts of white space used for each level, rather than just a simple count.

      • rmunn 1 hour ago
        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.
        • fc417fc802 30 minutes ago
          But it also feels arbitrary and annoyingly restrictive. On top of that there are at least 25 whitespace codepoints in UTF. Should your language really be opinionated about when, where, and in what order (for example) the "mongolian vowel separator" appears?
      • TZubiri 6 minutes ago
        For a 1024 byte implementation (and even way more complex impl.) You would just force one whitespace char, and definitely no mixing.
      • jubilanti 48 minutes ago
        > <space><space><tab><space> is different than <space><tab><space><space>

        in my view, both are the same, both `is` (or ===) an IndentationError raise

      • fc417fc802 28 minutes ago
        It's just a stack containing strings at the end of the day. Really not a big deal.
    • zephen 8 minutes ago
      > that criticism is usually posited by users of the language.

      Uhhh, no. Sure, it's posited by people who feel they are are forced to use it, but it's basically unlearning other syntax.

      Here's a study about people with no experience. They do better with python:

      https://www.researchgate.net/publication/262256894_An_Empiri...

      When the scala language made whitespace optional, it was very divisive, but now it's extremely well accepted.

      • TZubiri 3 minutes ago
        I meant users of languages ( application programmers) as opposed to compiler programmers, not python programmers specifically, so I'm including devs that use other languages and see in python a tool that they would consume.
  • hankbond 59 minutes ago
    Good use of free will and well-written. Very nice walkthrough austin!
  • Scubabear68 59 minutes ago
    I 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.

    • SPBS 31 minutes ago
      It’s true, the title should have said “Python-like”
      • happycube 5 minutes ago
        TBF the fizzbuzz code works just fine in CPython.
  • ni5arga 1 hour ago
    the blog post is pretty well-written! loved how he wrote about the the code-golfing part.