From: Adam Thompson <arthompson1990@gmail.com>
To: Chris Brannon <chris@the-brannons.com>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] -Wall
Date: Fri, 28 Jul 2017 19:19:57 +0000 [thread overview]
Message-ID: <20170728191957.GD20415@odin> (raw)
In-Reply-To: <8760efdcvx.fsf@the-brannons.com>
On Tue, Jul 25, 2017 at 09:45:54PM -0700, Chris Brannon wrote:
> Yes we should probably run with -Wall all the time.
> Passing -O2 and -D_FORTIFY_SOURCE=2 in CFLAGS exposes more warnings.
I wonder if we shouldn't compile with these flags on by default also? Just a thought, though I definitely think that we should enable all warnings by default and then explicitly suppress when we know we're ok.
Cheers,
Adam.
next prev parent reply other threads:[~2017-07-28 19:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 3:08 Karl Dahlke
2017-07-26 4:45 ` Chris Brannon
2017-07-28 19:19 ` Adam Thompson [this message]
2017-07-27 18:21 ` Geoff McLane
2017-07-28 5:51 ` Karl Dahlke
2017-07-28 19:24 ` Geoff McLane
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=20170728191957.GD20415@odin \
--to=arthompson1990@gmail.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=chris@the-brannons.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.
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).