Newsgroups: comp.lang.lisp,comp.lang.dylan,comp.lang.scheme
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!oitnews.harvard.edu!yale!yale.edu!news.ycc.yale.edu!imci3!newsfeed.internetmci.com!panix!news1.erols.com!howland.erols.net!cam-news-hub1.bbnplanet.com!news.mathworks.com!tank.news.pipex.net!pipex!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
X-Nntp-Posting-Host: pitcairn
Message-ID: <DwwqxM.89y@cogsci.ed.ac.uk>
Sender: cnews@cogsci.ed.ac.uk (C News Software)
Organization: HCRC, University of Edinburgh
References: <sjpw4hbzvo.fsf@alfresco.usask.ca> <4vp93n$fpk@snotra.harlequin.co.uk> <Pine.SOL.3.91.960828151930.18118A-100000@granby>
Date: Thu, 29 Aug 1996 16:24:58 GMT
Lines: 18
Xref: glinda.oz.cs.cmu.edu comp.lang.lisp:22437 comp.lang.dylan:7079 comp.lang.scheme:16660

In article <Pine.SOL.3.91.960828151930.18118A-100000@granby> WJ Bland <pmykwjb@unix.ccc.nottingham.ac.uk> writes:
>On 25 Aug 1996, mathew wrote:
>
>> >Why not   unite many  of these   "LISP"s under  one  umbrella?  It  is
>> >perfectly feasible  to define a  common core and various extensions to
>> >suite various needs.
>> 
>> True enough.  If your core is defined properly, you can extend the
>> language arbitrarily.
>> 
>This, of course, is what CL *should* have been--a core language,
>extendable by librarys, just like C.

Implementations could treat it that way now.

-- jd


