Re: info on byte-coded and other fast interpreters

acha@CS.CMU.EDU (Anurag Acharya)
19 Mar 91 22:50:36 GMT

          From comp.compilers
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)
| List of all articles for this month |
Newsgroups: comp.compilers
From: acha@CS.CMU.EDU (Anurag Acharya)
Keywords: interpreter, design
Organization: Carnegie Mellon University
References: <HAM.91Mar16102336@Neon.Stanford.EDU> <2321@fornax.UUCP>
Distribution: comp
Date: 19 Mar 91 22:50:36 GMT

The implementation of Oaklisp, an object-oriented dialect of Scheme,
was based on a fast bytecode interpreter.


check out


Kevin Lang and Barak Pearlmutter, "The Oaklisp language and implementation
manuals", Tech report CMU-CS-87-103 School of Computer Science
Carnegie Mellon University.


and


Kevin Lang and Barak Pearlmutter, "An object oriented scheme with first class
types", ACM conf on object-oriented systems, programming, languages and
applications, sept 1986, pp 1-8


anurag
--

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.