From: Nick <nospam@codesniffer.com>
To: Daniel Llorens <daniel.llorens@bluewin.ch>
Cc: gcc-help@gcc.gnu.org
Subject: Re: -Wzero-as-null-pointer-constant & extern "C" blocks
Date: Thu, 16 Oct 2014 03:30:00 -0000 [thread overview]
Message-ID: <1413430197.3155.1.camel@nimble.325Bayport> (raw)
In-Reply-To: <9A581557-C983-448B-A4C2-70AE229442E8@bluewin.ch>
On Mon, 2014-10-13 at 13:57 +0200, Daniel Llorens wrote:
> Hello,
>
> I tried using -Wzero-as-null-pointer-constant in a C++ program, but I got warnings in some C headers, even though they are wrapped in extern "C" blocks.
>
> Since there is no nullptr in C, wouldn't it make more sense to disable the warning within those blocks? Is there some option that I'm missing?
>
If the C headers are separated, you may be able to use -isystem to
locate them (instead of -I) which suppresses some warnings.
Nick
prev parent reply other threads:[~2014-10-16 3:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 11:57 Daniel Llorens
2014-10-13 12:02 ` Jonathan Wakely
2014-10-13 12:27 ` Daniel Llorens
2014-10-16 3:30 ` Nick [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=1413430197.3155.1.camel@nimble.325Bayport \
--to=nospam@codesniffer.com \
--cc=daniel.llorens@bluewin.ch \
--cc=gcc-help@gcc.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.
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).