From: Pavel Roskin <proski@gnu.org>
To: linux-sparse@vger.kernel.org
Subject: Apostrophes confuse preprocessor
Date: Thu, 12 Jul 2007 12:33:47 -0400 [thread overview]
Message-ID: <1184258027.9594.9.camel@dv> (raw)
Hello!
Sparse reports errors for apostrophes in preprocessor directives. To
make things worse, it suppresses all useful warnings in the file.
$ cat test.c
#error Don't do it
$ sparse test.c
test.c:1:13: error: Bad character constant
test.c:1:2: error: Don do it
$ gcc test.c
test.c:1:2: error: #error Don't do it
$
--
Regards,
Pavel Roskin
reply other threads:[~2007-07-12 16:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1184258027.9594.9.camel@dv \
--to=proski@gnu.org \
--cc=linux-sparse@vger.kernel.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 NNTP newsgroup(s).