Newsgroups: comp.lang.lisp
Path: cantaloupe.srv.cs.cmu.edu!bb3.andrew.cmu.edu!newsfeed.pitt.edu!gatech!newsfeed.internetmci.com!EU.net!peer-news.britain.eu.net!newsfeed.ed.ac.uk!edcogsci!jeff
From: jeff@cogsci.ed.ac.uk (Jeff Dalton)
Subject: Re: ISO/IEC CD 13816 -- ISLisp
Message-ID: <DKz582.4Gr.0.macbeth@cogsci.ed.ac.uk>
Organization: Centre for Cognitive Science, Edinburgh, UK
References: <9512211831.AA08925@near.net> <19951221T184722Z@arcana.naggum.no> <MAD.96Jan8130810@tanzanite.math.keio.ac.jp>
Date: Wed, 10 Jan 1996 16:45:37 GMT
Lines: 26

In article <MAD.96Jan8130810@tanzanite.math.keio.ac.jp> mad@math.keio.ac.jp writes:

> > |   Then that's what ISLisp is intended to be.
>
> > do you mean that ISLisp will cause IEEE Scheme and ANSI Common Lisp to go
> > away?  that's an amazing attitude, to put it mildly.  ISLisp will clutter
> > up the Lisp world even _more_ than the current set of standard and
> > non-standard Lisps do.
>
>Please don't extract sentence out of its context.  My sentence above
>should be read "(if you want single standard) then that's what ISLisp
>is intended to be."

What do you mean by "a single standard".  ISLisp is *not* supposed
to be a standard for all of Lisp; it's supposed to be a standard for
one language in the Lisp family.  That's one of the reasons it's
called "ISLisp" instead of "Lisp" (which would then be called "ISO
Lisp" and appear to be a standard for all of Lisp).

This was discussed explicitly at the first meeting of WG-16 (the
ISO committee that produced the ISLisp definition).

-- jeff



