Gnus development mailing list
 help / color / mirror / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Warning: `mapcar' called for effect; use `mapc' or `dolist'
Date: Mon, 22 Oct 2007 17:39:28 -0400	[thread overview]
Message-ID: <cjk5peesmn.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <200710222104.l9ML4cah025247@oogie-boogie.ics.uci.edu> (Dan Nicolaescu's message of "Mon, 22 Oct 2007 14:04:38 -0700")

Dan Nicolaescu wrote:

> Reiner Steib <reinersteib+gmane@imap.cc> writes:
[...]
>   > Hm, I can't reproduce the warning using `emacs-lisp-byte-compile' with
>   > GNU Emacs 23.0.50.6 (i686-pc-linux-gnu, GTK+ Version 2.10.6) of 2007-10-20.
>   > Too old?
>
> I can't either.

I see the warning only when bootstrapping (in an up-to-date CVS). If I
repeat the same commands as used during bootstrapping, except using
the dumped "emacs" instead of "bootstrap-emacs", I still don't see the
warning:

  cd lisp
  rm gnus/gnus-group.elc
  EMACSLOADPATH=$PWD ../src/emacs \
   -batch --no-site-file --multibyte -f batch-byte-compile-if-not-done \
   gnus/gnus-group.el

Something to do with custom perhaps?

Anyway, regardless of this, from having replaced some mapcars in the
non-gnus parts of the trunk, I can say that the replacement is not
just something that can be done automatically, someone should look at
the actual code in each case.

It shouldn't take very long, and ought to eliminate ~ 100/370 of the
current bootstrap warnings. (There's not much point if the gnus in the
Emacs CVS will soon be replaced with gnus trunk though.)

  reply	other threads:[~2007-10-22 21:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-20  6:43 Dan Nicolaescu
2007-10-22 12:13 ` Katsumi Yamaoka
2007-10-22 18:49   ` 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 [this message]
2007-10-23  1:01         ` Miles Bader
2007-10-23 10:39           ` Richard Stallman
2007-10-23 10:39         ` Richard Stallman
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-27 10:46           ` Rewriting gnus-group-highlight-line (was: Warning: `mapcar' called for effect; use `mapc' or `dolist') Reiner Steib
2007-10-27 23:41             ` Richard Stallman
2007-10-28  0:05           ` Reiner Steib
2007-10-23 10:39         ` Warning: `mapcar' called for effect; use `mapc' or `dolist' Richard Stallman
2007-10-31  7:46         ` 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
2007-10-27 13:34       ` Purpose of Gnus CVS branches (was: Warning: `mapcar' called for effect; use `mapc' or `dolist') Reiner Steib
2007-10-29  0:36         ` Purpose of Gnus CVS branches Katsumi Yamaoka
2007-10-28 16:58   ` Warning: `mapcar' called for effect; use `mapc' or `dolist' Dan Nicolaescu
2007-11-24 22:51     ` Removing obsolete `nnmail-spool-file' (was: Warning: `mapcar' called for effect; use `mapc' or `dolist') Reiner Steib

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=cjk5peesmn.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=dann@ics.uci.edu \
    --cc=ding@gnus.org \
    --cc=emacs-devel@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.
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).