From: Richard Stallman <rms@gnu.org>
Cc: yamaoka@jpl.org, emacs-pretest-bug@gnu.org,
monnier@iro.umontreal.ca, ding@gnus.org
Subject: Re: Change in bytecomp.el breaks Gnus
Date: Tue, 16 Nov 2004 11:49:22 -0500 [thread overview]
Message-ID: <E1CU6WA-0002PN-8K@fencepost.gnu.org> (raw)
In-Reply-To: <200411141729.iAEHTSQ24178@raven.dms.auburn.edu> (message from Luc Teirlinck on Sun, 14 Nov 2004 11:29:28 -0600 (CST))
Most warnings are of the "function may not be defined at runtime" or
"assignment to free variable" type. There are such an enormous amount
of them that we have, practically speaking, no choice but to assume
that they are bogus until proven non-bogus.
I have been eliminating the "free variable" warnings from many files
over the past couple of years. I have not tried to to so in calc
or rmail, because calc is big and I don't know it, and rmail is being
to a large extent rewritten.
Would others like to carry on with this work?
prev parent reply other threads:[~2004-11-16 16:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <877jouepy8.fsf@telia.com>
[not found] ` <b9yd5ymkq11.fsf@jpl.org>
2004-11-11 7:40 ` Katsumi Yamaoka
2004-11-11 11:18 ` Katsumi Yamaoka
2004-11-11 17:45 ` Luc Teirlinck
2004-11-11 21:55 ` Stefan
2004-11-11 22:41 ` Luc Teirlinck
2004-11-11 22:54 ` Luc Teirlinck
2004-11-12 0:22 ` Katsumi Yamaoka
2004-11-12 3:57 ` Stefan Monnier
2004-11-12 4:30 ` Katsumi Yamaoka
2004-11-13 23:03 ` Stefan
2004-11-14 0:14 ` Katsumi Yamaoka
2004-11-14 5:21 ` Stefan
2004-11-14 6:10 ` Katsumi Yamaoka
2004-11-14 6:36 ` Stefan
2004-11-14 13:44 ` Katsumi Yamaoka
2004-11-14 17:29 ` Luc Teirlinck
2004-11-14 19:17 ` Stefan Monnier
2004-11-15 14:00 ` Richard Stallman
2004-11-15 15:36 ` Stefan Monnier
2004-11-15 23:22 ` Miles Bader
2004-11-15 23:28 ` Stefan Monnier
2004-11-15 23:38 ` Miles Bader
2004-11-15 23:44 ` Stefan Monnier
2004-11-15 23:57 ` Luc Teirlinck
2004-11-16 1:29 ` Nick Roberts
2004-11-16 1:49 ` Luc Teirlinck
2004-11-16 2:19 ` Luc Teirlinck
2004-11-16 16:49 ` Richard Stallman [this message]
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=E1CU6WA-0002PN-8K@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=ding@gnus.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=yamaoka@jpl.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).