From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.esat.net!nslave.kpnqwest.net!nloc2.kpnqwest.net!nloc.kpnqwest.net!nmaster.kpnqwest.net!nreader3.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: Why is Scheme not a Lisp? References: <87u1rkl068.fsf@charter.net> Mail-Copies-To: never From: Erik Naggum Message-ID: <3225044146103845@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 18 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Mar 2002 21:35:34 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader3.kpnqwest.net 1016055334 193.71.199.50 (Wed, 13 Mar 2002 22:35:34 MET) NNTP-Posting-Date: Wed, 13 Mar 2002 22:35:34 MET Xref: archiver1.google.com comp.lang.lisp:28810 * Doug Quale You read "Scheme is a (dialect of) Lisp" to mean "Scheme is a member of the Lisp family", and argue as if someone has denied that Scheme is a member of the Lisp family. You have completely missed the point. If the meaning you have inferred from the statement that has caused so much hostility could have been stated plainly, nothing would have happened, because the way it is written is so often _misunderstood_ (relative to your understanding, at least), and it is the possible, even reasonable, interpretation of that stupidly phrased relationshpi that is under attack. You are barking up the wrong tree. Even eloquent barking does not change the tree. /// -- 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.