Subject: Re: Requirement for an executable stack-Lisp interpreters
From: rpw3@rpw3.org (Rob Warnock)
Date: Mon, 11 Sep 2006 22:43:41 -0500
Newsgroups: comp.lang.lisp
Message-ID: <Uaqdnfb9ib9wsZvYnZ2dnUVZ_s-dnZ2d@speakeasy.net>
Rob Thorpe <robert.thorpe@antenova.com> wrote:
+---------------
| I've never had a problem with this.  AFAIK Lisps don't generally
| assemble code on the stack.  They build some assembly language, maybe
| with a C compiler, get an assembler to make it into machine code, then
| use an OS call to append this to the running executable.
+---------------

GCL & ECL do this, I think.

+---------------
| Some may make machine code directly, I don't know.
+---------------

CMUCL, SBCL, and I'm pretty sure ACL, Lispworks, & Scieneer as well,
generate compiled code directly into memory. [Dunno 'bout Corman Lisp...]

Classically, most Lisps with compilers did generate compiled code
directly into memory.


-Rob

-----
Rob Warnock			<rpw3@rpw3.org>
627 26th Avenue			<URL:http://rpw3.org/>
San Mateo, CA 94403		(650)572-2607