Related articles |
---|
info on byte-coded and other fast interpreters ham@Neon.Stanford.EDU (1991-03-16) |
Re: info on byte-coded and other fast interpreters bremner@cs.sfu.ca (1991-03-19) |
Re: info on byte-coded and other fast interpreters acha@CS.CMU.EDU (1991-03-19) |
Re: info on byte-coded and other fast interpreters oz@nexus.yorku.ca (1991-03-19) |
Re: info on byte-coded and other fast interpreters andrew@brownvm.brown.edu (1991-03-20) |
Re: info on byte-coded and other fast interpreters adrianho@barkley.Berkeley.EDU (Adrian J Ho) (1991-03-21) |
Re: info on byte-coded and other fast interpreters eliot@cs.qmw.ac.uk (Eliot Miranda) (1991-03-24) |
Re: info on byte-coded and other fast interpreters bremner@cs.sfu.ca (1991-03-25) |
Newsgroups: | comp.compilers |
From: | Adrian J Ho <adrianho@barkley.Berkeley.EDU> |
In-Reply-To: | acha@CS.CMU.EDU's message of 19 Mar 91 22:50:36 GMT |
Keywords: | interpreter, design, lisp |
Organization: | Compilers Central |
References: | <HAM.91Mar16102336@Neon.Stanford.EDU> <2321@fornax.UUCP> <ACHA.91Mar19175036@DRAVIDO.CS.CMU.EDU> |
Date: | Thu, 21 Mar 91 02:08:39 -0800 |
For a (perhaps) more up-to-date reference, check out:
"The Oaklisp Implementation Guide", Barak Pearlmutter & Kevin Lang,
Jan 15, 1990.
This manual, along with the sources to Oaklisp and "The Oaklisp
Langauge Manual", can be found at:
f.gp.cs.cmu.edu: /usr/bap/oak/ftpable/ [128.2.250.164]
Note that this site, along with most others at CMU, imposes a curious
restriction in that you can't specify '..' in paths. You'll therefore
have to cd directly to the specified (no browsing 8-).
Also, I corresponded with Barak last month, and he mentioned that the
implementation of Oaklisp is also described in a chapter of "Topics in
Advanced Language Implementation" (ed. Peter Lee, MIT Press, 1990).
Good luck!
-----------------------------------------------------------------------------
Adrian Ho, EECS (pronounced "eeks!") Dept. Phone: (415) 642-5563
UC Berkeley adrianho@barkley.berkeley.edu
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.