[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: A Dylan implemented on Common Lisp
- To: firstname.lastname@example.org
- Subject: Re: A Dylan implemented on Common Lisp
- From: email@example.com (Jeff Dalton)
- Date: Tue, 7 Mar 1995 19:15:32 GMT
- Organization: AIAI, University of Edinburgh, Scotland
- References: <firstname.lastname@example.org>, <1995Mar6.email@example.com>, <firstname.lastname@example.org>
- Sender: email@example.com
In article <firstname.lastname@example.org> sef@CS.CMU.EDU (Scott Fahlman) writes:
> If the CL->Dylan mapping isn't 100%, maybe we could
> push hard to get Dylan changed so it would be.
>Push all you like. It won't happen. Having a Dylan-in-CL for some
>transitional period is not a good enough reason to preserve all the
>accumulated small irritations that have built up in Lisp over the
Contrary to the impression created by Scott's anti-Lisp propaganda,
Common Lisp eliminated most of the small irritations that had built
up over the years. (E.g. interpreters using different scope rules
than compilers) Some of the remaining "small irritations" (e.g.
nil being false) are not universally considered irritations.
In any case, a Dylan-in-CL can handle nil vs #f (Scott's example),
as Schemes-in-CL have shown.
Note that Scott Fahlman was one of the designers of Common Lisp
and had plenty of opportunities to eliminate any irritations that