From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Addition of preprocessor statements with SmPL
Date: Wed, 29 Oct 2014 11:07:39 +0100 [thread overview]
Message-ID: <5450BC6B.1060301@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1410291102110.2459@hadrien>
>> @Add_before_implementation@
>> identifier func;
>> type t;
>> @@
>> (
>> #define func BAR(func)
>> t func(...)
>> { ... }
>> |
>> +#define func BAR(func)
>> t func(...)
>> { ... }
>> )
>
> This doesn't work.
Interesting ...
> There is no kind of disjunction that includes a function definition in a branch.
Was I too optimistic that my suggestion with the specification of SmPL
alternatives should also work?
Regards,
Markus
next prev parent reply other threads:[~2014-10-29 10:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 18:24 [Cocci] Parsing errors in several headers Jean-Sébastien Pédron
2014-10-28 18:33 ` Julia Lawall
2014-10-28 18:51 ` Jean-Sébastien Pédron
2014-10-28 19:10 ` SF Markus Elfring
2014-10-28 19:23 ` Jean-Sébastien Pédron
2014-10-28 20:19 ` Julia Lawall
2014-10-29 8:29 ` SF Markus Elfring
2014-10-29 8:35 ` Jean-Sébastien Pédron
2014-10-29 8:45 ` [Cocci] Addition of preprocessor statements with SmPL SF Markus Elfring
2014-10-29 10:26 ` [Cocci] Parsing errors in several headers Julia Lawall
2014-10-29 10:57 ` [Cocci] Addition of preprocessor statements with SmPL Jean-Sébastien Pédron
2014-10-29 11:01 ` Julia Lawall
2014-10-29 11:07 ` Julia Lawall
2014-10-29 11:25 ` Jean-Sébastien Pédron
2014-10-29 12:26 ` Jean-Sébastien Pédron
2014-10-29 12:05 ` [Cocci] Parsing errors in several headers SF Markus Elfring
2014-10-29 9:45 ` [Cocci] Addition of preprocessor statements with SmPL SF Markus Elfring
2014-10-29 10:02 ` Julia Lawall
2014-10-29 10:07 ` SF Markus Elfring [this message]
2014-10-29 10:23 ` 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=5450BC6B.1060301@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.