From ... Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!news.tele.dk!small.news.tele.dk!134.222.94.5!npeer.kpnqwest.net!nreader1.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: What I want from my Common Lisp vendor and the Common Lisp community References: <3208226254834485@naggum.net> Mail-Copies-To: never From: Erik Naggum Message-ID: <3208266416884194@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 31 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 31 Aug 2001 17:06:58 GMT X-Complaints-To: newsmaster@Norway.EU.net X-Trace: nreader1.kpnqwest.net 999277618 193.71.66.49 (Fri, 31 Aug 2001 19:06:58 MET DST) NNTP-Posting-Date: Fri, 31 Aug 2001 19:06:58 MET DST Xref: archiver1.google.com comp.lang.lisp:15246 * Sam Steingold > All differences between "clisp -ansi" and ANSI CL are due to lack of > resources. This is a > We will gladly accept patches and constructive discussion towards full > ANSI compliance. Please subscribe to and write there. > This has been stated so many times that I fail to see the reason for > your rudeness. I installed the latest available version of CLISP for GNU/Debian unstable because I was going bananas over the incompetence of a web designer who was supposed to help us get a secure news server with a web interface for user registration up and running in two weeks and I needed something to help save the day. I am quite happy to say that CLISP saved the project and let me produce web pages efficiently and correctly, and I had no clue to how this should be done using available tools when I started, which is why I _had_ to use Common Lisp so I at least had some firm ground under my feet. However, what I quoted from the man page is precisely among the things that have put me off CLISP for many years. Remove the denigratory remarks about how ANSI CL is broken and how standard behavior "is not useful for actual everyday work". If I want somebody's snotty opinions on the standard, I shall ask for it. I do not want them in a man page for a purportedly conforming implementation that I want to use because I am excited about the language. This has to do with the _professionalism_ in the community, not with conformance or how right anyone are about their comments. Professionals set aside their personal opinions when they do their work and focus on the work at hand. ///