Newsgroups: comp.lang.dylan,comp.lang.lisp,comp.lang.lisp.mcl
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news2.near.net!news.mathworks.com!udel!gatech!howland.reston.ans.net!news.sprintlink.net!EU.net!uknet!festival!edcogsci!jeff
From: jeff@aiai.ed.ac.uk (Jeff Dalton)
Subject: Re: A Dylan implemented on Common Lisp
Message-ID: <D5qxvM.MIG@cogsci.ed.ac.uk>
Sender: usenet@cogsci.ed.ac.uk (C News Software)
Nntp-Posting-Host: bute.aiai.ed.ac.uk
Organization: AIAI, University of Edinburgh, Scotland
References: <3jirll$r0g@cantaloupe.srv.cs.cmu.edu> <2877601102@hoult.actrix.gen.nz> <ppotts-1003951810490001@198.11.57.140>
Date: Mon, 20 Mar 1995 16:02:09 GMT
Lines: 16
Xref: glinda.oz.cs.cmu.edu comp.lang.dylan:3800 comp.lang.lisp:17120 comp.lang.lisp.mcl:6678

In article <ppotts-1003951810490001@198.11.57.140> ppotts@frymulti.com (Paul R. Potts) writes:
>In article <2877601102@hoult.actrix.gen.nz>, Bruce@hoult.actrix.gen.nz
>(Bruce Hoult) wrote:
>
>> Sounds *exactly* like C++ and the process that turned C into it.
>
>Heh. Good analogy!

Not very.  For instance, what played the part of C to Common Lisp's C++?

It can't be Lisp, because there were a number of different Lisps of
various sizes and shapes (many of them quite small, btw).  MacLisp is
probably as close as you'll get, but then the move to Common Lisp
was not very like the process that turned C into C++.

-- jd
