From ... Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!npeer.kpnqwest.net!nreader2.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: I like WHEN/UNLESS Was: Promoting CL Was: What I want from my Common Lisp vendor and the Common Lisp community References: <3208404998010473@naggum.net> <9n33uu$rl3$0@216.39.145.192> <9n5im8$8nc$1@news.gte.com> Mail-Copies-To: never From: Erik Naggum Message-ID: <3208700608725248@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 26 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Sep 2001 17:43:33 GMT X-Complaints-To: newsmaster@Norway.EU.net X-Trace: nreader2.kpnqwest.net 999711813 193.71.66.49 (Wed, 05 Sep 2001 19:43:33 MET DST) NNTP-Posting-Date: Wed, 05 Sep 2001 19:43:33 MET DST Xref: archiver1.google.com comp.lang.lisp:15684 * John Foderaro > 'if' is not a macro, it's a special form. > > Try to replace the definition of a special form in your favorite lisp. What _are_ you talking about? > If I had exported code which required people to redefine a special form > in their Lisp to run it, I would have been criticized and correctly. Why? What is this "replace" and "redefine" about? > As it is I just used a macro which can be added to any Common Lisp and > thus makes my code a valid Common Lisp program. And shadow-importing the symbol if from a different package than the common-lisp package into your application package, with a new macro definition would _not_ have made it a valid Common Lisp program? I have often gotten the impression that you are still programming in some ancient pre-Common Lisp langauge and do not really know what is in Common Lisp these days, or at least do not use it, but I wonder if you have ever studied the standard to see what is there. Sometimes, "experience" can get a little stale. ///