From: Michael Williamson <michael.h.williamson@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: odd behavior
Date: Thu, 28 Aug 2014 21:20:00 -0000 [thread overview]
Message-ID: <CAKZygbd3AV0D9p+Btp_M52WG0GqOFPBdX=j496JiDjU+XZgy5Q@mail.gmail.com> (raw)
Hi,
Using gcc version 4.6.3 including the parameter -Wall, I discovered
that it gives a warning message for missing closing double quotes
inside sections of code that are not even used due to #if ... #endif
statements. That seems odd.
Just FYI,
-Mike
next reply other threads:[~2014-08-28 21:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 21:20 Michael Williamson [this message]
2014-08-29 5:37 ` Jędrzej Dudkiewicz
2014-08-29 9:12 ` Jonathan Wakely
2014-08-29 10:36 ` Jędrzej Dudkiewicz
2014-08-29 12:12 ` Segher Boessenkool
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='CAKZygbd3AV0D9p+Btp_M52WG0GqOFPBdX=j496JiDjU+XZgy5Q@mail.gmail.com' \
--to=michael.h.williamson@gmail.com \
--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).