Newsgroups: comp.ai,comp.ai.genetic,comp.ai.neural-nets,comp.lang.lisp,comp.lang.c++,comp.os.msdos.programmer,comp.lang.asm.x86,comp.unix.programmer,comp.ai.philosophy
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news.dfci.harvard.edu!camelot.ccs.neu.edu!nntp.neu.edu!news.eecs.umich.edu!panix!feed1.news.erols.com!howland.erols.net!usc!news.isi.edu!gremlin!shomase!jbarnett
From: jbarnett@nrtc.northrop.com (Jeff Barnett)
Subject: Re: Lisp is not an interpreted language
Message-ID: <E0torn.CK0@gremlin.nrtc.northrop.com>
Sender: news@gremlin.nrtc.northrop.com (Usenet News Manager)
Reply-To: jbarnett@charming.nrtc.northrop.com
Organization: Northrop Automation Sciences Laboratory
References: <327D00D8.4B9F@earthlink.net> <55qi3l$j5p@dawn.mmm.com> <3280FE73.1259@dma.isg.mot.com> <55t27r$dk9@godzilla.cs.nwu.edu> <jqbE0Iu9B.Awv@netcom.com> <32834C76.6247@dma.isg.mot.com> <56bv0i$lm0$1@goanna.cs.rmit.edu.au>
Date: Wed, 13 Nov 1996 18:59:46 GMT
Lines: 19
Xref: glinda.oz.cs.cmu.edu comp.ai:42153 comp.ai.genetic:10359 comp.ai.neural-nets:34550 comp.lang.lisp:23697 comp.lang.c++:226332 comp.os.msdos.programmer:81747 comp.lang.asm.x86:32462 comp.unix.programmer:52584 comp.ai.philosophy:48737

In article <56bv0i$lm0$1@goanna.cs.rmit.edu.au>, ok@goanna.cs.rmit.edu.au (Richard A. O'Keefe) writes:
|> Mukesh Prasad <mprasad@dma.isg.mot.com> writes:
|> >Ah, "compiling to native code" brings up a different issue,
|> >that of whether or not you want to allow eval in the
|> >language.  If you do, there are some sleigh of hands
|> >involved (like hiding an interpreter in your "compiled"
|> >executable.)
|> 
|> Wrong.  A *compiler* in the executable will do fine.
|> What's more, a *dynamically linked* compiler will also do fine,
|> so no space need actually be taken up in the object file.

Just a foolow up to the above:  in a LIsp I implemented for the old
IBM 360/370 line, eval just called the compiler, ran the native code
produced, marked the function for garbage collect, then returned the
values.  BTW, the reason for this was that I detested the way other
Lisp's had/enjoyed differences between compiler and eval semantics.

Jeff Barnett
