3 ms·
The implementations are short and simple for easy reading, so they are not the most efficient or practical. Early versions of the code had bugs, so you should
by nabla9 7y ago
The implementations are short and simple for easy reading, so they are not the most efficient or practical. Early versions of the code had bugs, so you should not use the old versions of the book.
- mhh__ 7y agoThe key is to do what Steven Muchnick did for his Compiler textbook: Write the algorithms in a made up programming language so no one can run them and find the bugs. I'm not being facetious, it's called ICAN, and as far as I can tell no compiler exists for it. Other than that it's a great book though, although maybe showing its age in that there isn't much discussion of OOO and ILP etc. And SSA.
- nabla9 7y agoDonald Knuth did it first. First with MIX, then with MMIX. http://mmix.cs.hm.edu/ http://mmix.cs.hm.edu/
- Dylan16807 7y agoIt's a fun reference, but it's very different. It's a CPU rather than a language, he implemented it, and it was designed to be easy to implement.
- analog31 7y agoAs I understand it, Lisp was originally expected to be a teaching or proof language with no implementation, then it got implemented. https://en.wikipedia.org/wiki/Lisp_(programming_language)#History https://en.wikipedia.org/wiki/Lisp_(programming_language)#Hi...
- lispm 7y agoNo, Lisp was developed from 1958 onwards as a list processing language for the IBM 704. http://jmc.stanford.edu/articles/lisp/lisp.pdf http://jmc.stanford.edu/articles/lisp/lisp.pdf Page 7: > The implementation of LISP began in Fall 1958. The original idea was to produce a compiler, but this was considered a major undertaking, and we needed some experimenting in order to get good conventions for subroutine linking, stack handling and erasure. Therefore, we started by hand-compiling various functions into assembly language and writing subroutines to provide a LISP ”environment”.