Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

(How to Write a (Lisp) Interpreter (In Python)) (2010)

norvig.com

Post reply on HN
Print view View original

41–50 of 73 posts

Re: (How to Write a (Lisp) Interpreter (In Python)) (2010)

#41

Post by embedding-shape »

chombier wrote: post #10

If you ever wondered how to write a programming language, this is probably the best resource to get started (and then of course Crafting Interpreters). See also part 2 https://norvig.com/lispy2.html

I've always found MAL ("Make-A-Lisp" https://github.com/kanaka/mal) a bit more approachable, probably because I was out after creating my own programming language before I've written much Python. It's language agnostic, and really easy to follow along with most programming languages out there, explaining everything as you progress.

That it's language agnostic and somehow matters feels weird now a lot of time (and experience I suppose) afterwards, but back when I only knew 1-2 languages by heart, also having to face understanding Python at the same time from Norvigs guide/reference made it slightly more complicated for me.

I use this as a litmus test now when coming across new languages (implementing MAL in the new language), as it's such an easy approach to practically test large parts of the new language, and there is always host-language-specific tricks you can learn along the way.

Re: (How to Write a (Lisp) Interpreter (In Python)) (2010)

#42

Post by dang »

Is it classics day or something? (Fine with us!)

Related:

(How to Write a (Lisp) Interpreter (In Python)) (2010) - https://news.ycombinator.com/item?id=39665939 - March 2024 (91 comments)

(How to Write a (Lisp) Interpreter (In Python)) (2010) - https://news.ycombinator.com/item?id=30443949 - Feb 2022 (9 comments)

(How to Write a (Lisp) Interpreter (In Python)) - https://news.ycombinator.com/item?id=30327437 - Feb 2022 (3 comments)

(How to Write a (Lisp) Interpreter (In Python)) - https://news.ycombinator.com/item?id=26036431 - Feb 2021 (1 comment)

How to Write a Lisp Interpreter In Python (2010) - https://news.ycombinator.com/item?id=20590439 - Aug 2019 (29 comments)

How to Write a Lisp Interpreter in Python (2010) - https://news.ycombinator.com/item?id=12777852 - Oct 2016 (28 comments)

How to Write a Lisp Interpreter in Python (2010) - https://news.ycombinator.com/item?id=7825054 - May 2014 (41 comments)

(How to Write a ((Better) Lisp) Interpreter (in Python)) - https://news.ycombinator.com/item?id=1746916 - Oct 2010 (10 comments)

(How to Write a (Lisp) Interpreter (in Python)) - https://news.ycombinator.com/item?id=1745322 - Sept 2010 (39 comments)

Re: (How to Write a (Lisp) Interpreter (In Python)) (2010)

#43

Post by timonoko »

My Lisp from 1975 was actually used in real world and highly lucrative. Gemini could read the source code, but it told that my code was piece of shit and cannot be implemented in 64-bit world without drastic changes, so it made an example. But that version was just too advanced and too complex as a study subject. There are already enuff good Lisps in the world, methinks.

https://github.com/timonoko/nokolisp

Re: (How to Write a (Lisp) Interpreter (In Python)) (2010)

#44

Post by Izmaki »

dang wrote: post #42

Is it classics day or something? (Fine with us!) Related: (How to Write a (Lisp) Interpreter (In Python)) (2010) - https://news.ycombinator.com/item?id=39665939 - March 2024 (91 comments) (How to Write a (Lisp) Interpreter (In Python)) (2010) - https://news.ycombinator.com/item?id=30443949 - Feb 2022 (9 comments) (How to Write a (Lisp) Interpreter (In Python)) - https://news.ycombinator.com/item?id=30327437 - Feb 202…

I feel like we need a vibe coded guide in this modern day and age.

Re: (How to Write a (Lisp) Interpreter (In Python)) (2010)

#47

Post by adamddev1 »

Interestingly enough, linguists also use Lisp-like parentheses or brackets to annotate sentence structures. Trees and brackets are isomorphic, as both phrase structure grammarians and the original SICP lectures pointed out.

The brackets in the title sentence would look a lot different though. ;-)

Post reply on HN