Newsgroups: comp.lang.dylan,comp.lang.lisp,comp.lang.lisp.mcl
Path: cantaloupe.srv.cs.cmu.edu!rochester!cornell!travelers.mail.cornell.edu!news.kei.com!news.mathworks.com!uunet!sytex!smcl
From: smcl@sytex.com (Scott McLoughlin)
Subject: Re: A Dylan implemented on Common Lisp
Message-ID: <gw3T2c2w165w@sytex.com>
Sender: bbs@sytex.com
Organization: Sytex Access Ltd.
References: <3jskca$q42@wstar.mil.wi.us>
Date: Sun, 12 Mar 1995 04:41:51 GMT
Lines: 25
Xref: glinda.oz.cs.cmu.edu comp.lang.dylan:3676 comp.lang.lisp:17039 comp.lang.lisp.mcl:6611

jpf@wstar.mil.wi.us (John P. Flanagan) writes:

> instead of delivering last rights, why not breath life into this new
> standard by focusing on the handful of corrections needed to make Common
> Lisp a mainstream delivery vehicle.  We should be resolving all the
> fixes needed for the next Common Lisp standard, not planning for a
> funeral.  Scott Falhman gave up on the process, not the language.
> -- 
> jpf.

Howdy,
This sounds like a very reasonable suggestion to me. Lisp is a
wonderful language. I don't think that being the best bit
twiddler is a prerequisite for being a popular, general purpose
language.  Lisp has been around long enough that lisp vendors
and users should have a pretty good idea of where it comes 
up short, how it might be tweaked to compensate for these
short comings, how it might be modularized or layered, how
it might better interact with popular host operating systems,
etc. 

=============================================
Scott McLoughlin
Conscious Computing
=============================================
