From: Eli Zaretskii <eliz@gnu.org>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: -Wall
Date: Tue, 05 Apr 2016 17:35:43 +0300 [thread overview]
Message-ID: <8360vwnmww.fsf@gnu.org> (raw)
In-Reply-To: <m3oa9o4i95.fsf@gnus.org> (message from Lars Magne Ingebrigtsen on Tue, 05 Apr 2016 09:39:02 +0200)
> From: Lars Magne Ingebrigtsen <larsi@gnus.org>
> Date: Tue, 05 Apr 2016 09:39:02 +0200
> Cc: emacs-devel@gnu.org
>
> I still think that warnings should be enabled by default (on Linux), but
> they shouldn't be treated as errors.
I disagree. "gcc -Wall" is at times very noisy and tends to flag
perfectly valid C as suspect. The noise level sometimes makes it hard
to find real problems drowned in the sea of false alarms.
I usually compile once with -Wall after significant changes, and that
is enough to catch any real issues.
next prev parent reply other threads:[~2016-04-05 14:35 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 ` Eli Zaretskii [this message]
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 ` -Wall John Wiegley
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
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=8360vwnmww.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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).