From: John Wiegley <jwiegley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Philipp Stephani <p.stephani2@gmail.com>, emacs-devel@gnu.org
Subject: Re: -Wall
Date: Tue, 05 Apr 2016 08:09:25 -0700 [thread overview]
Message-ID: <m2r3ekum6y.fsf@newartisans.com> (raw)
In-Reply-To: <83y48sm7u2.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 05 Apr 2016 17:46:45 +0300")
>>>>> Eli Zaretskii <eliz@gnu.org> writes:
>> I'm very much in favor of addressing and eliminating all warnings on as many
>> platforms as possible.
>>
>> That'll be a challenge. When I compile with clang -Weverything, I get
>> ~90,000 warnings.
> I don't even think it's a worthy use of our resources. C compilers move
> towards more and more noisy defaults, so the real challenge is to come up
> with a set of switches that produce a high enough signal-to-noise ratio. I'm
> not saying that the current default is that sweet spot, but -Wall, let alone
> -Weverything, is certainly not it.
-Weverything may be a bit too much, but the alternative -- that of ignoring
warnings because there are too many of them -- is also not a good choice. We
should find the sweet spot we want to adhere to, and then make it clean.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2016-04-05 15:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 18:22 -Wall Lars Magne Ingebrigtsen
2016-04-04 18:51 ` -Wall Paul Eggert
2016-04-04 18:58 ` -Wall Lars Magne Ingebrigtsen
2016-04-05 0:20 ` -Wall Paul Eggert
2016-04-05 7:39 ` -Wall Lars Magne Ingebrigtsen
2016-04-05 14:35 ` -Wall Eli Zaretskii
2016-04-05 15:12 ` -Wall Paul Eggert
2016-04-06 11:49 ` -Wall Lars Magne Ingebrigtsen
2016-04-06 12:02 ` -Wall Stefan Monnier
2016-04-07 5:16 ` -Wall Paul Eggert
2016-04-04 23:22 ` -Wall John Wiegley
2016-04-05 13:16 ` -Wall Philipp Stephani
2016-04-05 14:46 ` -Wall Eli Zaretskii
2016-04-05 15:09 ` John Wiegley [this message]
2016-04-05 14:54 ` -Wall 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2r3ekum6y.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=p.stephani2@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.