all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Ralf Angeli <angeli@caeruleus.net>
Cc: Glenn Morris <rgm@gnu.org>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-devel@gnu.org
Subject: Re: declare-function from included file
Date: Wed, 19 Mar 2008 13:42:02 -0700	[thread overview]
Message-ID: <200803192042.m2JKg3Cm010626@sallyv1.ics.uci.edu> (raw)
In-Reply-To: <87r6e6wj3j.fsf@photon.caeruleus.net> (Ralf Angeli's message of "Wed, 19 Mar 2008 21:32:16 +0100")

Ralf Angeli <angeli@caeruleus.net> writes:

  > * Stefan Monnier (2008-03-19) writes:
  > 
  > > This said, if you have a need for *many* declare-function, then maybe
  > > the problem is elsewhere and you should report it (maybe Emacs could be
  > > more clever about how to detect when a warning is needed).
  > 
  > In case of RefTeX most of the warnings stem from calls to AUCTeX
  > functions in reftex-auc.el.  (The functions are only used if
  > `reftex-plug-into-AUCTeX' is non-nil.)  So this is not really Emacs'
  > fault of not being clever enough.

In CVS trunk reftex compiles without warnings.  There are 10
`declare-function's in reftex*el, 8 of which are in reftex-auc.el.
That does not sound like too much, it's hard to see that it's even worth discussing...




  reply	other threads:[~2008-03-19 20:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-16 18:23 declare-function from included file Ralf Angeli
2008-03-19  0:47 ` Glenn Morris
2008-03-19 18:57   ` Ralf Angeli
2008-03-19 19:30     ` Stefan Monnier
2008-03-19 20:32       ` Ralf Angeli
2008-03-19 20:42         ` Dan Nicolaescu [this message]
2008-03-19 21:00           ` Ralf Angeli
2008-03-19 21:19             ` Dan Nicolaescu
2008-03-19 21:45               ` Ralf Angeli
2008-03-19 22:18                 ` Dan Nicolaescu

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=200803192042.m2JKg3Cm010626@sallyv1.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=angeli@caeruleus.net \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.