From ...
Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!news.tele.dk!small.news.tele.dk!134.222.94.5!npeer.kpnqwest.net!reader3.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> <87itf1a2fh.fsf_-_@piracy.red-bean.com> <99fb3972.0109021504.bba92d0@posting.google.com> <3208475381413624@naggum.net> <MPG.15fca7683180ccba989705@news.dnai.com> <3208511830109687@naggum.net> <MPG.15fd2f7aaf808fc8989707@news.dnai.com> <87r8tow5ej.fsf@orion.bln.pmsf.de> <MPG.15fd8c7e2f4c12f298970b@news.dnai.com> <871ylnx1pw.fsf@orion.bln.pmsf.de> <MPG.15fdcc0ddc1825c598970d@news.dnai.com> <Df6l7.32821$aZ.8664688@typhoon.tampabay.rr.com> <9n33uu$rl3$0@216.39.145.192> <MPG.15fec26834416ffc9896b2@news.dnai.com> <87lmjun4eo.fsf@nkapi.internal> <m3y9nueis2.fsf@localhost.localdomain> <3208694796835930@naggum.net> <ey3d755oazu.fsf@cley.com>
Mail-Copies-To: never
From: Erik Naggum <erik@naggum.net>
Message-ID: <3208697937973361@naggum.net>
Organization: Naggum Software, Oslo, Norway
Lines: 18
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 16:59:01 GMT
X-Complaints-To: newsmaster@Norway.EU.net
X-Trace: reader3.kpnqwest.net 999709141 193.71.66.49 (Wed, 05 Sep 2001 18:59:01 MET DST)
NNTP-Posting-Date: Wed, 05 Sep 2001 18:59:01 MET DST
Xref: archiver1.google.com comp.lang.lisp:15680

* Tim Bradshaw <tfb@cley.com>
> I've recently had to deal with some code which did exactly this.

  Geez, somebody _did_ that?  For real?  That is just sickening.

  I guess I should have "commented" the code and explained why I thought it
  would be an obvious "bad joke", on par with #define BEGIN { in C, but
  which would illustrate that having implicit progns is not such a big deal.

  This might also be a good time to state that I really want to use progn
  in multi-form consequents and alternatives, to increase the readability
  of complex if forms.  That is, we already have all the mechanisms we need
  to identify more complex forms.  And wrapping a single form in a progn is
  real easy with a real editor.  Just like loop forms are hard to navigate,
  so are keyword-based "separators".  But I guess some people want progn to
  go away so hard they just have to reinvent it badly.

///