From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Skipping of source code between preprocessor statements?
Date: Wed, 04 Mar 2015 14:13:31 +0100 [thread overview]
Message-ID: <54F704FB.8020305@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1503040708010.3976@hadrien>
>> In which contexts does the syntax allow the use of single quotes
>> for the C programming language?
>
> As far as I can tell, all.
Are they only valid within comments and string literals?
>> How would you like to handle text within the construct "#if 0 / #endif"
>> by the analysis tool?
>
> There is a flag for choosing whether to do this.
Do you refer to the undocumented command line parameter "noif0-passing"?
Regards,
Markus
next prev parent reply other threads:[~2015-03-04 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 1:27 [Cocci] EXN question Stan Sieler
2015-02-25 6:25 ` Julia Lawall
2015-02-25 8:05 ` [Cocci] Challenges around preprocessor statements? SF Markus Elfring
2015-03-02 23:54 ` [Cocci] EXN question Julia Lawall
2015-03-04 11:48 ` [Cocci] Skipping of source code between preprocessor statements? SF Markus Elfring
2015-03-04 12:08 ` Julia Lawall
2015-03-04 13:13 ` SF Markus Elfring [this message]
2015-03-04 16:47 ` Julia Lawall
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=54F704FB.8020305@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=cocci@systeme.lip6.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.