Coccinelle Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: jean-sebastien.pedron@dumbbell.fr (Jean-Sébastien Pédron)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Addition of preprocessor statements with SmPL
Date: Wed, 29 Oct 2014 12:25:02 +0100	[thread overview]
Message-ID: <5450CE8E.1040902@dumbbell.fr> (raw)
In-Reply-To: <alpine.DEB.2.10.1410291205580.26234@hadrien>

On 29.10.2014 12:07, Julia Lawall wrote:
> On Wed, 29 Oct 2014, Jean-S?bastien P?dron wrote:
> 
>> On 29.10.2014 11:26, Julia Lawall wrote:
>>>> I wanted to be able to re-run spatch on an already patched content. The
>>>> use case is to add new function prototypes manually and run spatch to
>>>> handle the associated #define automatically.
>>>
>>> I think that you could do the following:
>>>
>>> @r@
>>> identifier func;
>>> @@
>>> #define        func    BAR(func)
>>>
>>> @s@
>>> identifier r.func;
>>> position p;
>>> @@
>>>
>>> func at p(...) {...}
>>>
>>> @@
>>> identifier func;
>>> position p != s.p;
>>> @@
>>>
>>> +#define        func    BAR(func)
>>> func(...) { ... }
> 
> Sorry, typo here.  It should be func at p(...) { ... }

You're right, it's working now! Thank you :)

> What is more unpleasant is that at least in my version of Coccinelle, it
> indents the function definition.

Here, with 1.0.0rc19, I don't have this problem.

-- 
Jean-S?bastien P?dron

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: OpenPGP digital signature
URL: <https://systeme.lip6.fr/pipermail/cocci/attachments/20141029/e4311a64/attachment.asc>

  reply	other threads:[~2014-10-29 11:25 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 [this message]
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
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=5450CE8E.1040902@dumbbell.fr \
    --to=jean-sebastien.pedron@dumbbell.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox