From ... Path: archiver1.google.com!news2.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!news2.kpn.net!news.kpn.net!nslave.kpnqwest.net!nloc2.kpnqwest.net!nloc.kpnqwest.net!nmaster.kpnqwest.net!nreader2.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: [NEWBIE] - Lisp or CLOS ? References: <2382dbbe.0111260641.497d93cd@posting.google.com> <87vgfxmrxz.fsf@kometknut.neitileu.no> Mail-Copies-To: never From: Erik Naggum Message-ID: <3215783792255809@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 21 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, 26 Nov 2001 17:16:34 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader2.kpnqwest.net 1006794994 193.71.66.49 (Mon, 26 Nov 2001 18:16:34 MET) NNTP-Posting-Date: Mon, 26 Nov 2001 18:16:34 MET Xref: archiver1.google.com comp.lang.lisp:20972 * Erik Haugan | CLOS _is_ Lisp, so when you study CLOS, you study Lisp. I think this is one of those situations where it is important to point out that CLOS is _Common_ Lisp. Although no other Lisps are relevant in the third millennium :), I would be cautious about those highlighted "is" relationships. Much can go seriously wrong if you believe in bad ones. | You really should learn the basics of Common Lisp before moving on to | classes, generic functions and methods, but there are lots of advanced | topics you don't have to be an expert in to get started, e g macros, | conditions, files and pretty printing. This is good advice. /// -- The past is not more important than the future, despite what your culture has taught you. Your future observations, conclusions, and beliefs are more important to you than those in your past ever will be. The world is changing so fast the balance between the past and the future has shifted.