From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: cl in message.el, etc
Date: Fri, 19 Apr 2002 18:13:10 -0400 [thread overview]
Message-ID: <87adrz72x5.fsf@alum.wpi.edu> (raw)
In-Reply-To: <87g01r74d7.fsf@alum.wpi.edu>
Josh Huber <huber@alum.wpi.edu> writes:
> (loop for regexp in mft-regexps and recipient in recipients
> thereis (when (string-match regexp recipient)
> recipient))))
>
> Since It's a lot shorter, and (I think) easier to read.
Oh, and it also doesn't work. ;) Here's the working version:
(loop for regexp in mft-regexps thereis
(loop for recipient in recipients
thereis (when (string-match regexp recipient)
recipient)))))
what do other people think?
BTW, the execution speed seems to be about the same. For me most of
the speed hit is taken in the gnus-find-subscribed-addresses
function. (since I have so many groups)
ttyl,
--
Josh Huber
next prev parent reply other threads:[~2002-04-19 22:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-19 21:41 Josh Huber
2002-04-19 22:13 ` Josh Huber [this message]
2002-04-20 3:43 ` Daniel Pittman
2002-04-20 15:14 ` Josh Huber
2002-04-20 16:03 ` Daniel Pittman
2002-04-20 17:34 ` Josh Huber
2002-04-21 2:28 ` Daniel Pittman
2002-04-22 8:18 ` Kai Großjohann
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=87adrz72x5.fsf@alum.wpi.edu \
--to=huber@alum.wpi.edu \
/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).