From: Ralf Angeli <angeli@caeruleus.net>
To: Dan Nicolaescu <dann@ics.uci.edu>
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 22:45:02 +0100 [thread overview]
Message-ID: <87fxumwfq9.fsf@photon.caeruleus.net> (raw)
In-Reply-To: <200803192119.m2JLJuUL000802@sallyv1.ics.uci.edu> (Dan Nicolaescu's message of "Wed, 19 Mar 2008 14:19:56 -0700")
* Dan Nicolaescu (2008-03-19) writes:
> Ralf Angeli <angeli@caeruleus.net> writes:
>
> > In RefTeX's own repository compiling still emits warnings.
>
> What's wrong with just copying the declare-functions from emacs CVS to
> get rid of them?
I've already explained this in this thread.
> > It's not just the `declare-function' stuff I'm after. RefTeX contains a
> > lot of `defvar' statements which are only there for the sake of the byte
> > compiler.
> >
> > And I'd like to put those into a separate file as well along with
> > stuff like `declare-function' calls.
>
> defvars work, they are well known by any elisp hackers.
> Why develop a new facility the everyone looking at the code will have to
> figure out?
Oh, I see putting them in a separate file does not work either. I guess
I'll have to live with the cruft then.
--
Ralf
next prev parent reply other threads:[~2008-03-19 21:45 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
2008-03-19 21:00 ` Ralf Angeli
2008-03-19 21:19 ` Dan Nicolaescu
2008-03-19 21:45 ` Ralf Angeli [this message]
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
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=87fxumwfq9.fsf@photon.caeruleus.net \
--to=angeli@caeruleus.net \
--cc=dann@ics.uci.edu \
--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 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).