Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Christoph Conrad <christoph.conrad@gmx.de>
Cc: Justus@piater.name, ding@gnus.org
Subject: Re: nnir.el cleanup
Date: Sun, 20 Apr 2008 22:02:36 +0200	[thread overview]
Message-ID: <v9bq44i9b7.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87k5isa5vc.fsf@ID-24456.user.uni-berlin.de> (Christoph Conrad's message of "Sun, 20 Apr 2008 17:39:19 +0200")

[ The following message is a courtesy copy of an article that has
  been posted to news:gmane.emacs.gnus.general as well. ]

On Sun, Apr 20 2008, Christoph Conrad wrote:

>> Could someone look into the compiler warnings, please? I don't
>> understand what the warnings about the arguments are about.
>
> With CVS Emacs i get mostly warnings, interestingly. Some mapcars are
> only used for side-effect and can be replace by mapc. 

As we want to move nnir.el to lisp/ in Gnus trunk, it will be synced
to Emacs 23 (trunk).  Thus, we should fix the warning that Emacs 23
produces. 

> The 'reference to free variable' are due moving code outside a
> context where the variables where defined as parameter or in a
> `let'-binding. Simply make a new `let' binding. I do not get any
> 'argument' warnings here.

I'm not sure that I understand what you have in mind.  Could you
provide a patch that fixes/silences the Emacs 23 compiler warnings?

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



  reply	other threads:[~2008-04-20 20:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87y77fiszu.fsf@ID-24456.user.uni-berlin.de>
     [not found] ` <87lk3fvw4l.fsf@ID-24456.user.uni-berlin.de>
     [not found]   ` <873apmapq9.fsf_-_@ID-24456.user.uni-berlin.de>
     [not found]     ` <x8tfxtm2mqc.fsf@tool.montefiore.ulg.ac.be>
2008-04-16 10:50       ` FIX Christoph Conrad
2008-04-16 18:22         ` nnir.el swish++ interface broken (was: FIX) Reiner Steib
2008-04-17  7:20           ` nnir.el swish++ interface broken Justus-bulk
2008-04-17  7:37             ` Christoph Conrad
2008-04-17 18:01               ` Christoph Conrad
2008-04-19 17:36             ` Reiner Steib
2008-04-20  7:48               ` nnir.el cleanup (was Re: nnir.el swish++ interface broken) Justus
2008-04-20 10:09                 ` nnir.el cleanup Reiner Steib
2008-04-20 15:39                   ` Christoph Conrad
2008-04-20 20:02                     ` Reiner Steib [this message]
2008-04-22 17:52                       ` Christoph Conrad
2008-04-24 18:06                         ` Reiner Steib
2008-04-24 18:34                           ` Christoph Conrad
2008-04-24 18:17                         ` Compiler warnings in nnir.el (was: nnir.el cleanup) Reiner Steib
2008-04-25  2:27                           ` Compiler warnings in nnir.el Stefan Monnier
2008-04-20 11:03                 ` nnir.el cleanup (was Re: nnir.el swish++ interface broken) Christoph Conrad
2008-04-21 13:40                 ` Christoph Conrad

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=v9bq44i9b7.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Justus@piater.name \
    --cc=Reiner.Steib@gmx.de \
    --cc=christoph.conrad@gmx.de \
    --cc=ding@gnus.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).