From: martin rudalics <rudalics@gmx.at>
To: Glenn Morris <rgm@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: suppressing byte-compiler warnings about undefined functions
Date: Tue, 13 Nov 2007 10:31:09 +0100 [thread overview]
Message-ID: <47396EDD.6020007@gmx.at> (raw)
In-Reply-To: <ah8x52wzcd.fsf@fencepost.gnu.org>
>>checkdoc-scan could be far far more efficient. It should scan all
^
`checkdec' will be likely confused more often with `checkdoc'. I think
a different term should be used. Also, wouldn't it be reasonable to add
`declare-variable' as well? I'm not arguing for consistency here. But
we could get rid of comments talking about "byte-compiler warnings" or
"pacify byte-compiler". And the intention of some `(defvar variable)'s
without such comments would become more clear.
next prev parent reply other threads:[~2007-11-13 9:31 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 [this message]
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
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=47396EDD.6020007@gmx.at \
--to=rudalics@gmx.at \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.org \
--cc=rms@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).