Newsgroups: comp.lang.lisp,comp.lang.scheme,comp.lang.dylan
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news4.ner.bbnplanet.net!cam-news-hub1.bbnplanet.com!howland.erols.net!EU.net!usenet2.news.uk.psi.net!uknet!usenet1.news.uk.psi.net!uknet!uknet!newsfeed.ed.ac.uk!edcogsci!jeff
From: jeff@cogsci.ed.ac.uk (Jeff Dalton)
Subject: Re: Common LISP: The Next Generation
Message-ID: <DxHo4q.zA.0.macbeth@cogsci.ed.ac.uk>
Organization: HCRC, University of Edinburgh
References: <322E34DC.2191@mindspring.com> <322f1671.44808029@news> <joswig-0609961112310001@news.lavielle.com>
Date: Mon, 9 Sep 1996 23:34:02 GMT
Lines: 14
Xref: glinda.oz.cs.cmu.edu comp.lang.lisp:22644 comp.lang.scheme:16798 comp.lang.dylan:7185

In article <joswig-0609961112310001@news.lavielle.com> joswig@lavielle.com (Rainer Joswig) writes:

>Other Lisp systems have delivery tools, too. There is
>a price to pay for having a sophisticated *integrated* development
>environment and wishing to deliver small executables.
>But who says that you can't import a Lisp to C compiler
>into your development environment (like CLICC) and
>create small Lisp applications. But they would lack all
>features that makes Common Lisp "dynamic".

Why would they?  Many of the dynamic features are just assignment,
after all.

-- jd
