Any programmer reading this will think "Could this be done for code?" followed by "What code would stand up to it?" followed by "Maybe I could write some..." http://cognitivemedium.com/srs-mathematics
-
-
Replying to @paulg
The original LISP eval certainly would stand up to it.
1 reply 0 retweets 6 likes -
Replying to @michael_nielsen
You'd get a surprise though. Did you know there was a bug in it?
1 reply 0 retweets 5 likes -
Replying to @paulg
Oh my, I had no idea! I've read that reasonably carefully, too. Not to mention having written an implementation, both in Python, and in the resulting mini-Lisp.
1 reply 0 retweets 1 like -
Replying to @michael_nielsen
I don't remember where it was, but I encountered it when I tried to translate JMC's eval into CL. You could presumably find it by comparing that code to JMC's. https://gist.github.com/adlai/3cd4fcbca02aab926dab …
2 replies 0 retweets 1 like -
Replying to @paulg @michael_nielsen
JMC spoke of Steve Russell "fixing bugs" when he hand-translated eval into machine language to make the first Lisp interpreter. I've always assumed it was the same bug but I have no way of knowing.
1 reply 0 retweets 3 likes
It turns out I described the bug, and some other things I discovered, in the notes of "The Roots of Lisp." In the last clause of eval, (evlis (cdr e) a) should be just (cdr e). There's also a variable capture in his maplist. http://lib.store.yahoo.net/lib/paulgraham/jmc.ps …
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.