Newsgroups: comp.lang.dylan,comp.lang.java,comp.lang.lisp
Path: cantaloupe.srv.cs.cmu.edu!rochester!cornellcs!travelers.mail.cornell.edu!news.kei.com!news.mathworks.com!newsfeed.internetmci.com!news.sprintlink.net!in2.uu.net!EU.net!uknet!newsfeed.ed.ac.uk!edcogsci!jeff
From: jeff@cogsci.ed.ac.uk (Jeff Dalton)
Subject: Re: GC, Java, etc.
Message-ID: <DGnB3F.Csp@cogsci.ed.ac.uk>
Organization: Centre for Cognitive Science, Edinburgh, UK
References: <LUDEMANN.95Oct6140930@expernet26.expernet.com>  <DGApp8.J41@undergrad.math.uwaterloo.ca>  <DGDGEB.6no@undergrad.math.uwaterloo.ca> <45ltru$osk@camelot.ccs.neu.edu>  <DGGpDx.IGE@undergrad.math.uwaterloo.ca>	<activisDGJr2B.4Ex@netcom.com> <4kUj=Ay00iV8A84qw1@andrew.cmu.edu>
Date: Wed, 18 Oct 1995 13:05:59 GMT
Lines: 22
Xref: glinda.oz.cs.cmu.edu comp.lang.dylan:5465 comp.lang.java:1978 comp.lang.lisp:19579

"Noah L. Gibbs" <angelbob+@andrew.cmu.edu> writes:

>Excerpts from netnews.comp.lang.dylan: 16-Oct-95 Re: GC, Java, etc. by
>ActiVision@netcom.com 
>> I find this almost impossible to credit, as it's been a good decade or more
>> since I've seen a Scheme or Common Lisp that _didn't_ include a compiler!

>    This also depends on what you mean by compiler.  I consider, e.g.
>Allegro CommonLISP to be interpreted, although the professor of our course
>assured us it was "incrementally compiled".  However, the speed, interact-
>ivity, and every other empirical test indicated it was an interpreter.

What do you mean by "Allegro CommonLISP"?  The one from Franz Inc that
runs on Suns and a number of other machines definitely includes a
compiler to native code.  If you call everything that's incrementally
compiled or interactive (or maybe only both) an interpreter, you're
just wrong.  As for speed, compiled code isn't much slower than
compiled C.

Did you actually compile anything, by the way?

-- jd
