The author mentioned that this page is not quite ready yet -- I think he meant to give the code a bit more polish, and I guess that's why lispy.html has reader's comments while this doesn't.
I can also believe it's "in progress." I wanted to know more about the picture tagged as "First Lisp Interpreter." Checking the link revealed that it is amazingly to the dynamic(?) Facebook(!) resize of:
call/cc, for one, certainly needs more work. Maybe at least a mention that this implements escape continuations and not the full continuations that, say, DrRacket implements.
I really enjoy Norvig's writing. Will wait for it to be finished.
Full continuations would be a major change to the code, and would disallow calling Python functions that call Scheme back. (E.g. right now you could add 'map' to the toplevel by just binding Python's map().) But yes, I'd mention the difference.
Comments
The author mentioned that this page is not quite ready yet -- I think he meant to give the code a bit more polish, and I guess that's why lispy.html has reader's comments while this doesn't.
I can also believe it's "in progress." I wanted to know more about the picture tagged as "First Lisp Interpreter." Checking the link revealed that it is amazingly to the dynamic(?) Facebook(!) resize of:
http://commons.wikimedia.org/wiki/File:Steve_Russell-PDP-1-2...
(So it's Steve Russell in the front of the PDP-1)
and I wouldn't expect the Facebook service to be used in the final version.
call/cc, for one, certainly needs more work. Maybe at least a mention that this implements escape continuations and not the full continuations that, say, DrRacket implements.
I really enjoy Norvig's writing. Will wait for it to be finished.
Full continuations would be a major change to the code, and would disallow calling Python functions that call Scheme back. (E.g. right now you could add 'map' to the toplevel by just binding Python's map().) But yes, I'd mention the difference.