Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Using CL in Gnus (was: gnus-agentize versus emacs 20 mapc)
Date: Wed, 26 Nov 2003 12:34:21 +0100	[thread overview]
Message-ID: <v9y8u3cqiq.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <b9yoeuzvpvw.fsf@jpl.org>

On Wed, Nov 26 2003, Katsumi Yamaoka wrote:
>>>>>>	Kevin Ryde <user42@zip.com.au> wrote:

[ spam-stat.el ]
>> Looks like this one has its own trickery to drag in 'cl when required.
>> With dgnushack doing it perhaps that's no longer wanted.
>
> That is only for smap-stat and Emacs 20 users.  However, mapc
> you wrote about is in gnus-agent.el and gnus.el which may be
> used by most of Gnus and Emacs 20 users.

IMHO, the point isn't how many users are affected by loading cl, but
that all GNU Emacs packages (thus Gnus) should not load it at run time
at all:

,----[ (info "(cl)Overview") in Emacs CVS HEAD ]
|    *Please note:* the "CL" functions are not standard parts of the
| Emacs Lisp name space, so it is legitimate for users to define them
| with other, conflicting meanings.  To avoid conflicting with those user
| activities, we have a policy that packages installed in Emacs must not
| load "CL" at run time.  (It is ok for them to load "CL" at compile time
| only, with `eval-when-compile', and use the macros it provides.)  If
| you are writing packages that you plan to distribute and invite
| widespread use for, you might want to observe the same rule.
`----

OTOH, Gnus 5.10.x (labeled Gnus 5.11) will be included in Emacs 21.y
where the relevant functions for `spam-stat.el' (gethash
hash-table-count make-hash-table mapc puthash) are built-in functions
already.  So I'm not sure how relevant it is to avoid mapc and friends
in Gnus 5.10.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/




  reply	other threads:[~2003-11-26 11:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-24 23:29 gnus-agentize versus emacs 20 mapc Kevin Ryde
2003-11-24 23:57 ` Katsumi Yamaoka
2003-11-25  3:45   ` Kevin Greiner
2003-11-25  4:18     ` Katsumi Yamaoka
2003-11-25 21:47     ` Kevin Ryde
2003-11-26  2:13       ` Katsumi Yamaoka
2003-11-26 11:34         ` Reiner Steib [this message]
2003-11-26 12:23           ` Using CL in Gnus Katsumi Yamaoka
2003-11-26 17:38             ` Reiner Steib
2003-11-26 19:46               ` Karl Pflästerer
2003-11-27 22:41                 ` Reiner Steib
2003-11-28 16:30                   ` Karl Pflästerer
2003-11-28 17:08                     ` Jesper Harder
2003-11-29  8:04                       ` Miles Bader
2003-11-29  9:10                         ` Jesper Harder
2003-11-29 12:37                           ` Miles Bader
2003-12-01 21:23               ` Ted Zlatanov
2003-12-01 22:54                 ` Katsumi Yamaoka
2003-11-30 13:22           ` Using CL in Gnus (was: gnus-agentize versus emacs 20 mapc) Per Abrahamsen
2003-11-28 21:31         ` gnus-agentize versus emacs 20 mapc Kevin Ryde

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=v9y8u3cqiq.fsf@marauder.physik.uni-ulm.de \
    --to=4.uce.03.r.s@nurfuerspam.de \
    --cc=reiner.steib@gmx.de \
    /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).