From ... Path: archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-01!supernews.com!newsfeed.online.be!newsfeed.vmunix.org!newsfeed.belnet.be!news.belnet.be!news.brutele.be!nmaster.kpnqwest.net!nnum.kpnqwest.net!EU.net!nreader2.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: Common Lisp reference manual References: <85heks7oxg.fsf@junk.nocrew.org> Mail-Copies-To: never From: Erik Naggum Message-ID: <3231565105993078@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 19 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 May 2002 08:58:27 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader2.kpnqwest.net 1022576307 193.71.199.50 (Tue, 28 May 2002 10:58:27 MET DST) NNTP-Posting-Date: Tue, 28 May 2002 10:58:27 MET DST Xref: archiver1.google.com comp.lang.lisp:34014 * Lars Brinkhoff | What would the best Common Lisp reference manual for the working | programmer be? If you are not intimately familiar with the Standard, as in the (Xanalys) HyperSpec, you are simply not a professional Common Lisp. (Franz Inc also has a version of the standard with a very different visual appeal -- I have recently heard people who much prefer it, so it ought to be mentioned.) I actually think a serious, professional programmer has a copy of the actual standards relevant for his work, either in the company library or a personal copy. Languages have specifications. Applications have documentation. Good programmers read the specification. Good users read the documentation. -- 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. 70 percent of American adults do not understand the scientific process.