From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!news2.kpn.net!news.kpn.net!nslave.kpnqwest.net!nloc.kpnqwest.net!nmaster.kpnqwest.net!nreader1.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: Little doubts with "if" clause References: <9ca131c.0112010155.19eeb52@posting.google.com> <20011201051600.F2173@emu> <3216248368595666@naggum.net> Mail-Copies-To: never From: Erik Naggum Message-ID: <3216312794772355@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 41 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 Dec 2001 20:13:16 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader1.kpnqwest.net 1007323996 193.71.66.49 (Sun, 02 Dec 2001 21:13:16 MET) NNTP-Posting-Date: Sun, 02 Dec 2001 21:13:16 MET Xref: archiver1.google.com comp.lang.lisp:21721 * Coby Beck | You've never been in my kill-file! My mistake -- I thought had said you did, once. My apologies. | I guess it was mostly the passive tense "it is advised" phrase that made | me want to point out that is hardly a universal axiom of IF that more | than on form in a branch means it should be a COND. I hope style is not considered "axiomatic" anywhere. * Erik Naggum > The lack of an implicit progn in the if form is a hint that cond, which > has an implicit progn for each branch, would be more appropriately used > for bodies with side-effects and if for expressions. | This is a strong argument, though one more from tradition than other | stylistic concerns. | I still like the strong visual signal an IF form gives you that there are | two and only two branches. That seems like a reasonable rationale, but it appears to me (i.e., pretty weak certainy) that most of the uses have one branch with a single form, like return or error, and the other a larger body of something. I tend to use one-branch conditionals and know that that branch terminates the function or asks the operator to fix an error -- sometimes one can turn an error into a continuable error, then the function should not simply error out | Variety is the spice of life, I like very much that lisp provides so many | ways to express your code. I second that. /// -- 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.