Newsgroups: comp.lang.lisp,comp.lang.dylan,comp.lang.scheme
Path: cantaloupe.srv.cs.cmu.edu!bb3.andrew.cmu.edu!newsfeed.pitt.edu!gatech!nntp04.primenet.com!nntp.primenet.com!newspump.sol.net!uwm.edu!math.ohio-state.edu!howland.erols.net!netcom.com!vrotney
From: vrotney@netcom.com (William Paul Vrotney)
Subject: Re: Common LISP: The Next Generation
In-Reply-To: haertel@ichips.intel.com's message of 28 Aug 1996 17:02:18 GMT
Message-ID: <vrotneyDww5su.AJG@netcom.com>
Organization: NETCOM On-line Communication Services (408 261-4700 guest)
References: <sjpw4hbzvo.fsf@alfresco.usask.ca> <4vp93n$fpk@snotra.harlequin.co.uk> <3050214712631064@arcana.naggum.no> <501u2q$3vk@news.jf.intel.com>
Date: Thu, 29 Aug 1996 08:48:29 GMT
Lines: 15
Sender: vrotney@netcom22.netcom.com
Xref: glinda.oz.cs.cmu.edu comp.lang.lisp:22422 comp.lang.dylan:7066 comp.lang.scheme:16644

In article <501u2q$3vk@news.jf.intel.com> haertel@ichips.intel.com (Mike Haertel) writes:

> 
> I think the real reason most Lisp implementations produce huge
> executables is not that it's not possible, but that Lisp implementors
> have, for whatever reason, chosen not to work on that particular
> problem.

Actually they have, it's just that they were stopped in mid stream by the
C++ wave.


-- 

William P. Vrotney - vrotney@netcom.com
