Code like this makes me a little upset. It'll completely break on simple cases: `(print "To close the REPL, type (quit).")` being an obvious example.
I get that it's a toy example, but all too often it slides into tricking people that hard* problems are trivial.
* - I'm aware that tokenization has been a solved problem for decades—what I'm trying to say is that it takes quite a bit more thought than the four-line implementation suggests.
Re:Little Lisp interpreter
by _murphys_law_ on Tuesday May 26, 2015 @06:47PM
(#9608186)
I thought the article did very well in providing an introductory resource to students hoping to learn more about the structure of an interpreter. On the other hand, if one wanted a nearly identical, and possibly more rigorous approach to learning about implementing a "tiny lisp" Peter Norvig's lispy implementation is a wonderful resource: http://norvig.com/lispy.html ... of course any computer scientist studying languages should also have read Mcarthy - http://www.cse.sc.edu/~mgv/csce330f13/micromanualLISP.pdf
I get that it's a toy example, but all too often it slides into tricking people that hard* problems are trivial.
* - I'm aware that tokenization has been a solved problem for decades—what I'm trying to say is that it takes quite a bit more thought than the four-line implementation suggests.
How does the interpreter know that the (1 2) part is a list, and not an application of 1 to 2?
http://www.biwascheme.org/