From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!colt.net!newspeer.clara.net!news.clara.net!news-hub.cableinet.net!blueyonder!amsnews01.chello.com!trev!skynet.be!skynet.be!ossa.telenet-ops.be!nmaster.kpnqwest.net!nreader3.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: Keywords and macros References: <3CAE051B.E2022B60@yale.edu> Mail-Copies-To: never From: Erik Naggum Message-ID: <3227029532064004@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 20 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Apr 2002 21:05:16 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader3.kpnqwest.net 1018040716 193.71.199.50 (Fri, 05 Apr 2002 23:05:16 MET DST) NNTP-Posting-Date: Fri, 05 Apr 2002 23:05:16 MET DST Xref: archiver1.google.com comp.lang.lisp:31135 * Drew McDermott | Point 1: I was under the impression that the 'loop' macro's many "local | syntax markers" were exported from the :common-lisp package. Someone | reminded us that this is not so. To quote from Allegro's ANSI CL | hyperspec (no doubt Kent's usual lucid spec): | | Loop keywords are not true keywords1; they are special symbols, | recognized by name rather than object identity, that are meaningful | only to the loop facility. A loop keyword is a symbol but is | recognized by its name (not its identity), regardless of the packages | in which it is accessible. Why is this such a big deal to you? /// -- 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. Post with compassion: http://home.chello.no/~xyzzy/kitten.jpg