From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Challenges around preprocessor statements?
Date: Wed, 25 Feb 2015 09:05:09 +0100 [thread overview]
Message-ID: <54ED8235.9010001@users.sourceforge.net> (raw)
In-Reply-To: <F3E7ABF7-5E64-4AEF-B9CF-AE8CA0CE458B@allegro.com>
> We were quite surprised that spatch / coccinelle isn't ignoring stuff
> (I won't say "code", because it's often non-code English text)
> within "#if 0 / #endif" blocks, and feel this is a design flaw.
The Coccinelle software works on a different abstraction level.
There is another feature request for text skipping in the waiting queue.
https://github.com/coccinelle/coccinelle/issues/20
Are there any more use cases to consider?
Would you eventually like to adjust source code between preprocessor
statements?
Regards,
Markus
next prev parent reply other threads:[~2015-02-25 8:05 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 ` SF Markus Elfring [this message]
2015-03-02 23:54 ` 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
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=54ED8235.9010001@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.