From: Alan Mackenzie <acm@muc.de>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: Glenn Morris <rgm@gnu.org>, emacs-devel@gnu.org
Subject: Re: suppressing byte-compiler warnings about undefined functions
Date: Sun, 11 Nov 2007 16:10:42 +0000 [thread overview]
Message-ID: <20071111161042.GA1653@muc.de> (raw)
In-Reply-To: <200711111551.lABFpS6L011370@oogie-boogie.ics.uci.edu>
Hi, Dan!
On Sun, Nov 11, 2007 at 07:51:24AM -0800, Dan Nicolaescu wrote:
> Alan Mackenzie <acm@muc.de> writes:
> > On Fri, Nov 09, 2007 at 07:55:08PM -0500, Glenn Morris wrote:
> > > Here's an attempt at a method to allow for suppressing of
> > > byte-compiler warnings about undefined functions.
> > > I haven't yet written the function to check that functions are
> > > actually defined in the specified files, but I imagine it would be
> > > straightforward.
> > As a matter of interest, there has been this sort of functionality
> > in cc-bytecomp.el (written by Martin Stjernholm) for some time. In
> > particular, `cc-bytecomp-defun' and `cc-bytecomp-defvar', whose
> > prime use is suppressing compiler warnings.
> What is the advantage of (cc-bytecomp-defvar VARIABLE) over plain
> (defvar VARIABLE)?
You can have the variable "defined" solely for the duration of the
byte-compilation. This is useful for `xemacs-foo' and `gnu-emacs-bar'
if your file.el is portable. It's useful for core Emacs
variables/functions defined in a file which isn't currently loaded.
> > It might be sensible to reuse this.
> Would that be possible without editing all elisp files in emacs?
Yes, absolutely! But it'll need some files to be edited. ;-)
--
Alan Mackenzie (Ittersbach, Germany).
next prev parent reply other threads:[~2007-11-11 16:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 0:55 suppressing byte-compiler warnings about undefined functions Glenn Morris
2007-11-10 3:13 ` Stefan Monnier
2007-11-10 17:54 ` Richard Stallman
2007-11-11 1:11 ` Glenn Morris
2007-11-11 4:00 ` Glenn Morris
2007-11-11 19:33 ` Richard Stallman
2007-11-13 4:20 ` Glenn Morris
2007-11-13 9:31 ` martin rudalics
2007-11-14 5:32 ` Glenn Morris
2007-11-14 14:53 ` Stefan Monnier
2007-11-15 3:07 ` Richard Stallman
2007-11-17 3:58 ` Glenn Morris
2007-11-17 23:30 ` Richard Stallman
2007-11-13 20:02 ` Richard Stallman
2007-11-13 21:05 ` Stefan Monnier
2007-11-14 5:30 ` Glenn Morris
2007-11-15 3:06 ` Richard Stallman
[not found] ` <ur9oddrnmg0.fsf@mothra.ics.uci.edu>
2007-11-19 0:39 ` byte-compiler warnings about undefined functions can now be silenced Glenn Morris
2007-11-19 9:04 ` martin rudalics
2007-11-24 3:12 ` Glenn Morris
2007-11-19 19:02 ` Richard Stallman
2007-11-20 4:05 ` Glenn Morris
2007-11-19 19:33 ` Jay Belanger
2007-11-19 20:46 ` Glenn Morris
2007-11-20 12:12 ` Richard Stallman
2007-11-11 8:46 ` suppressing byte-compiler warnings about undefined functions Alan Mackenzie
2007-11-11 15:51 ` Dan Nicolaescu
2007-11-11 16:10 ` Alan Mackenzie [this message]
2007-11-11 16:18 ` Dan Nicolaescu
2007-11-11 18:32 ` Dan Nicolaescu
2007-11-11 23:54 ` Richard Stallman
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=20071111161042.GA1653@muc.de \
--to=acm@muc.de \
--cc=dann@ics.uci.edu \
--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.
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).