From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!news2.kpn.net!news.kpn.net!nslave.kpnqwest.net!nloc.kpnqwest.net!nmaster.kpnqwest.net!nreader2.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: Why is Scheme not a Lisp? References: <87pu28kzjy.fsf@charter.net> <87eliokv9v.fsf@charter.net> <87sn73c40c.fsf@charter.net> <3225233908428331@naggum.net> Mail-Copies-To: never From: Erik Naggum Message-ID: <3225433911106510@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 11 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Mar 2002 09:51:39 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader2.kpnqwest.net 1016445099 193.71.199.50 (Mon, 18 Mar 2002 10:51:39 MET) NNTP-Posting-Date: Mon, 18 Mar 2002 10:51:39 MET Xref: archiver1.google.com comp.lang.lisp:29355 * William D Clinger | It probably surprises you that I was one of the people who pointed out | the need for this restriction when Common Lisp was being standardized. Yes, that surprises me. But thanks for the information, and also that it got that way. /// -- In a fight against something, the fight has value, victory has none. In a fight for something, the fight is a loss, victory merely relief.