Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Glenn Morris <rgm@gnu.org>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: declare-function in files from Gnus (hashcash.el, imap.el)
Date: Sat, 01 Dec 2007 19:35:52 +0100	[thread overview]
Message-ID: <v9ve7i5kl3.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <adk5nz5n6y.fsf@fencepost.gnu.org> (Glenn Morris's message of "Fri, 30 Nov 2007 18:27:17 -0500")

On Sat, Dec 01 2007, Glenn Morris wrote:

> Reiner Steib wrote:
>
>> Maybe we could add (defalias 'declare-function 'ignore ...) (like in
>> Emacs 22.2) to `gnus/lisp/dgnushack.el' (in Gnus).
>
> I think that's the best idea. 

I'm not so sure.  Several problems come to my mind:

- `dgnushack.el' itself is considered harmful by some people.  Instead
  of compiling all lisp files at once, the make procedure should maybe
  call "emacs ... -f batch-byte-compile FILE.el" for each file as the
  Makefile in Emacs does.

- When compiling with Emacs 22.1 (or Emacs 21) even with `ignore', I
  get additional bogus warnings:

  /usr/bin/emacs-22.1 -Q -batch --eval \
  "(unless (fboundp 'declare-function) (defalias 'declare-function 'ignore))" \
  -f batch-byte-compile emacs/lisp/net/imap.el 

  In toplevel form:
  imap.el:969:19:Warning: reference to free variable `sasl-find-mechanism'
  imap.el:970:19:Warning: reference to free variable `sasl-mechanism-name'
  imap.el:971:19:Warning: reference to free variable `sasl-make-client'
  imap.el:971:57:Warning: reference to free variable `name'
  imap.el:971:62:Warning: reference to free variable `service'
  imap.el:971:70:Warning: reference to free variable `server'
  imap.el:972:19:Warning: reference to free variable `sasl-next-step'
  imap.el:972:54:Warning: reference to free variable `step'
  imap.el:973:19:Warning: reference to free variable `sasl-step-data'
  imap.el:974:19:Warning: reference to free variable `sasl-step-set-data'
  imap.el:974:52:Warning: reference to free variable `data'
  
  In end of data:
  imap.el:2969:1:Warning: the following functions are not known to be defined:
      mechanism, client, step, sasl-mechanism-name, sasl-make-client,
      sasl-next-step, sasl-step-data, sasl-step-set-data
  Wrote [...]/emacs/lisp/net/imap.elc

- When loading `*.el' or evaluating the buffer (sometimes necessary to
  get a better backtrace or for testing), you get:

  eval-buffer: Symbol's function definition is void: declare-function

- Doesn't it work for XEmacs?  When building an XEmacs package,
  `dgnushack.el' isn't used, I'd guess.

> This would let us add similar statements to files in gnus/. 

Please don't do this yet.  Let's wait until we come to a good solution
in this thread and until Miles has synched the current
declare-function changes to Gnus and we see which (other) problems it
may cause for the stand-alone Gnus.

> (I just posted to ding suggesting this; may as well use this thread
> to discuss it rather than that one.)

Yes.  I hadn't seen your message when writing/sending mine.

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

  reply	other threads:[~2007-12-01 18:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-30 22:56 Reiner Steib
2007-11-30 23:27 ` Glenn Morris
2007-12-01 18:35   ` Reiner Steib [this message]
2007-12-01 18:54     ` Dan Nicolaescu
2007-12-01 20:35       ` Glenn Morris
2007-12-01 20:40         ` Dan Nicolaescu
2007-12-01 21:50     ` Glenn Morris
2007-12-01 21:42 ` syncing from Emacs to Gnus [was Re: declare-function in files from Gnus (hashcash.el, imap.el)] Glenn Morris
2007-12-01 23:22   ` syncing from Emacs to Gnus Reiner Steib
2007-12-02 14:56     ` Stefan Monnier
2007-12-02 18:39     ` Richard Stallman
2007-12-03  2:25       ` Stefan Monnier
2007-12-03 18:43         ` Richard Stallman
2007-12-03 18:59           ` Stefan Monnier
2007-12-06  2:12             ` Richard Stallman
     [not found] ` <fir8np$3br$1@ger.gmane.org>
     [not found]   ` <200712011634.lB1GYCkr018222@oogie-boogie.ics.uci.edu>
     [not found]     ` <87mysuwdcx.fsf@neutrino.caeruleus.net>
     [not found]       ` <E1IybxG-0000AT-DD@fencepost.gnu.org>
     [not found]         ` <87ac27w4lz.fsf@neutrino.caeruleus.net>
     [not found]           ` <E1IywKa-0006WN-2v@fencepost.gnu.org>
     [not found]             ` <87u00eufga.fsf@neutrino.caeruleus.net>
     [not found]               ` <200712022237.lB2MbNC8016800@oogie-boogie.ics.uci.edu>
     [not found]                 ` <v9d4tnxtiw.fsf@marauder.physik.uni-ulm.de>
     [not found]                   ` <200712032340.lB3Ne3Vt009200@oogie-boogie.ics.uci.edu>
2007-12-05 20:35                     ` declare-function in files from Gnus (hashcash.el, imap.el) Reiner Steib
2007-12-05 21:01                       ` Glenn Morris
2007-12-08 19:42                         ` Reiner Steib
2007-12-08 22:58                           ` Dan Nicolaescu
2007-12-09  2:20                             ` Glenn Morris
2007-12-09 20:10                               ` Austin Frank
2007-12-09 21:22                                 ` 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=v9ve7i5kl3.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@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).