From: Paul Eggert <eggert@cs.ucla.edu>
To: rms@gnu.org
Cc: 23640@debbugs.gnu.org, andrewjmoreton@gmail.com
Subject: bug#23640: 25.1.50; Getting rid of compiler warnings
Date: Mon, 6 Jun 2016 07:45:00 -0700 [thread overview]
Message-ID: <a252fa8c-b8a6-b278-50fe-fe48c77b8236@cs.ucla.edu> (raw)
In-Reply-To: <E1b8ftl-0001If-Oo@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 540 bytes --]
On 06/02/2016 08:35 PM, Richard Stallman wrote:
> one single macro UNUSED will work for integers and Lisp_Object
Yes, that works, though UNUSED is a confusing name to attach to a
variable, as the variable is actually used. A better name is UNINIT,
indicating that the variable is uninitialized. Similarly, NONVOLATILE
could indicate that a variable is not volatile, in cases where GCC would
otherwise complain. The attached patch would suffice to omit all uses of
the IF_LINT macro in the Emacs source, if that's a style you prefer.
[-- Attachment #2: 0001-Replace-IF_LINT-by-NONVOLATILE-and-UNINIT.patch --]
[-- Type: application/x-patch, Size: 21057 bytes --]
next prev parent reply other threads:[~2016-06-06 14:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-28 18:40 bug#23640: 25.1.50; Getting rid of compiler warnings Ken Brown
2016-05-28 18:57 ` Eli Zaretskii
2016-05-28 21:47 ` Ken Brown
2016-05-29 22:43 ` Ken Brown
2016-05-30 11:39 ` Ken Brown
2016-05-30 14:41 ` Ken Brown
2016-05-30 16:20 ` Ken Brown
2016-05-30 23:29 ` Paul Eggert
2016-05-31 0:11 ` Ken Brown
2016-05-31 8:03 ` Andy Moreton
2016-05-31 22:22 ` Richard Stallman
2016-05-31 0:15 ` Paul Eggert
2016-06-01 8:35 ` Paul Eggert
2016-06-01 20:37 ` Richard Stallman
2016-06-01 21:10 ` Paul Eggert
2016-06-02 12:05 ` Andy Moreton
2016-06-03 3:35 ` Richard Stallman
2016-06-06 14:45 ` Paul Eggert [this message]
2016-06-07 6:19 ` Richard Stallman
2016-06-07 7:15 ` Paul Eggert
2016-06-08 4:00 ` Richard Stallman
2016-06-08 7:18 ` Paul Eggert
2016-06-08 17:06 ` Richard Stallman
2016-06-01 8:55 ` Paul Eggert
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=a252fa8c-b8a6-b278-50fe-fe48c77b8236@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=23640@debbugs.gnu.org \
--cc=andrewjmoreton@gmail.com \
--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).