From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: cl
Date: 27 Jan 1999 18:03:21 +0100 [thread overview]
Message-ID: <m37lu8sl5y.fsf@quimbies.gnus.org> (raw)
Gowrsh. I really should re-read CLtL2.
(let ((vars (some-ting))
var)
(while (setq var (pop vars))
...))
which I usually write, vs
(dolist (var (some-thing))
...)
And the latter is even a macro in cl-macs that expands to nice
Emacs-lisp bytecodes.
(And the first form even assumes that there are no non-nil elements in
the list. Which is true everywhere I use it, but that makes the
dolist thing even more elegant.)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Magne Ingebrigtsen
next reply other threads:[~1999-01-27 17:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-27 17:03 Lars Magne Ingebrigtsen [this message]
1999-01-27 19:10 ` cl Jan Vroonhof
1999-01-27 21:01 ` cl Justin Sheehy
1999-01-28 7:37 ` cl Lars Magne Ingebrigtsen
1999-01-28 18:16 ` cl Hrvoje Niksic
1999-12-14 4:21 cl Katsumi Yamaoka
1999-12-14 11:01 ` cl Hrvoje Niksic
1999-12-14 11:37 ` cl Katsumi Yamaoka
1999-12-14 18:55 ` cl Jan Vroonhof
1999-12-14 22:43 ` cl Katsumi Yamaoka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m37lu8sl5y.fsf@quimbies.gnus.org \
--to=larsi@ifi.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).