From: Richard Stallman <rms@gnu.org>
To: Miles Bader <miles@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Warning: `mapcar' called for effect; use `mapc' or `dolist'
Date: Tue, 23 Oct 2007 22:50:11 -0400 [thread overview]
Message-ID: <E1IkWJv-0001Fc-PU@fencepost.gnu.org> (raw)
In-Reply-To: <buo640y6pe8.fsf@dhapc248.dev.necel.com> (message from Miles Bader on Tue, 23 Oct 2007 20:28:47 +0900)
In Common-Lisp, I think you use (declare (special VAR ...)) to indicate
a localized use of dynamic binding (as the first thing inside the let
form where it is bound).
Since Elisp already uses `declare' for some other things, it would seem
reasonable to also use it to inform the byte compiler that an apparently
local variable is known to be accessed non-locally.
I would not mind adding this feature to Emacs Lisp.
But I still think that part of Gnus should get a total rewrite
using a different mechanism.
next prev parent reply other threads:[~2007-10-24 2:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200710200643.l9K6h9gk021348@oogie-boogie.ics.uci.edu>
[not found] ` <b4mtzojbb4c.fsf@jpl.org>
2007-10-22 18:49 ` Warning: `mapcar' called for effect; use `mapc' or `dolist' Reiner Steib
2007-10-22 20:07 ` Dan Nicolaescu
2007-10-22 20:55 ` Reiner Steib
2007-10-22 21:04 ` Dan Nicolaescu
2007-10-22 21:39 ` Glenn Morris
2007-10-23 1:01 ` Miles Bader
2007-10-23 10:39 ` Richard Stallman
2007-10-23 11:28 ` Miles Bader
2007-10-24 2:50 ` Richard Stallman [this message]
2007-10-23 10:39 ` Richard Stallman
[not found] ` <E1IkHAF-00040s-KJ@fencepost.gnu.org>
2007-10-27 10:46 ` Risky variables in Gnus (was: Warning: `mapcar' called for effect; use `mapc' or `dolist') Reiner Steib
2007-10-27 23:41 ` Richard Stallman
2007-10-28 0:02 ` Risky variables in Gnus Reiner Steib
2007-11-01 20:51 ` Reiner Steib
2007-10-31 7:46 ` Warning: `mapcar' called for effect; use `mapc' or `dolist' Richard Stallman
2007-10-31 20:30 ` Reiner Steib
2007-10-31 21:19 ` Glenn Morris
2007-11-01 2:35 ` Katsumi Yamaoka
2007-10-24 19:28 ` Reiner Steib
2007-10-24 22:18 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1IkWJv-0001Fc-PU@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).