All of lore.kernel.org
 help / color / mirror / Atom feed
From: mstefani@redhat.com (Michael Stefaniuc)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Replacing one (specific!) type with another
Date: Wed, 5 Oct 2016 18:39:25 +0200	[thread overview]
Message-ID: <57F52CBD.7020204@redhat.com> (raw)
In-Reply-To: <87shsa7p71.fsf@thinkpad.rath.org>

On 10/05/2016 06:09 PM, Nikolaus Rath wrote:
> On Oct 05 2016, Julia Lawall <julia.lawall@lip6.fr> wrote:
>> On Tue, 4 Oct 2016, Nikolaus Rath wrote:
>>
>>> Hello,
>>>
>>> In a set of C files, I would like to replace each instance of one type
>>> (struct fasel_foo) with another type (struct fasel_bar). For instance,
>>>
>>> char* fasel_foo_print(struct fasel_foo *ptr) {
>>>     // ...
>>>    return "this struct fasel_foo string should not change";
>>> }
>>>
>>> should become
>>>
>>> char* fasel_foo_print(struct fasel_bar *ptr) {
>>>     // ...
>>>    return "this struct fasel_foo string should not change";
>>> }
>>>
>>>
>>> Based on the LWN articles that I've read, this seems like the perfect
>>> use-case for coccinelle. However, somehow I'm struggling to write a
>>> patch for this. All the documentation that I could get my hands on seems
>>> to describe more abstract changes that require the use of variables -
>>> but as far as I can tell, I need something much simpler:
>>>
>>> @@
>>> "struct fasel_foo must be a type name!"
>>> @@
>>> - struct fasel_foo
>>> + struct fasel_bar
>>>
>>>
>>> ...if only I knew what to put between the @@.
>>
>> Put nothing :)  From the word struct it should figure out that it is
>> working on a type.
> 
> Oh, great! Thanks!
> 
> 
> This solves my problem, but it makes me wonder how this generalizes to
> other problems. For example, 
> 
> 1. What would I need to do if I don't want to replace a struct but
>    something typedef'd? (my_type *ptr --> new_type *ptr).
Easy

@@
typedef my_type, new_type;
@@
- my_type
+ new_type

> 2. ..and how would I go about if instead of the type, I want to replace
>    a variable name? (my_type *ptr --> my_type *pointer).
Depends on the exact circumstance. But that's easy to figure out. I
recommend the workshop papers and tutorials from
http://coccinelle.lip6.fr/papers.php; I wish I would have had those when
I started with coccinelle.

bye
	michael

  reply	other threads:[~2016-10-05 16:39 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-05  3:27 [Cocci] Replacing one (specific!) type with another Nikolaus Rath
2016-10-05  5:45 ` Julia Lawall
2016-10-05 16:09   ` Nikolaus Rath
2016-10-05 16:39     ` Michael Stefaniuc [this message]
2016-10-05 17:21     ` [Cocci] Replacing one variable name " SF Markus Elfring
2016-10-05 22:34       ` Nikolaus Rath
2016-10-06  5:42         ` SF Markus Elfring
2016-10-06  5:56         ` Julia Lawall
2016-10-05 20:02     ` [Cocci] Replacing one (specific!) type " Julia Lawall
2016-10-05 22:38       ` Nikolaus Rath
2016-10-06  5:55         ` Julia Lawall
2016-10-08  3:16           ` Nikolaus Rath
2016-10-08  5:50             ` Julia Lawall
2016-10-08 20:45               ` Nikolaus Rath
2016-10-08 21:23                 ` Julia Lawall
2016-10-09  6:32                 ` SF Markus Elfring
2016-10-08  6:48             ` [Cocci] Usage of "expressions" and "identifiers" with SmPL SF Markus Elfring
2016-10-08  6:57               ` Julia Lawall
     [not found]               ` <alpine.DEB.2.10.1610080850470.7750@hadrien>
2016-10-08  7:49                 ` SF Markus Elfring
2016-10-08  7:56                   ` Julia Lawall
2016-10-08  8:26                     ` SF Markus Elfring
2016-10-08  8:38                       ` Julia Lawall
2016-10-08  9:25                         ` SF Markus Elfring
2016-10-08 20:28                           ` Nikolaus Rath
2016-10-09  7:49                             ` SF Markus Elfring
2016-10-09 20:38                               ` Nikolaus Rath
2016-10-10  6:48                                 ` SF Markus Elfring
2016-10-10  6:50                                   ` Julia Lawall
2016-10-06  6:30         ` [Cocci] Replacing one (specific!) type with another SF Markus Elfring
2016-10-08  4:22       ` Nikolaus Rath
2016-10-08  5:31         ` Julia Lawall
2016-10-08 20:52           ` Nikolaus Rath
2016-10-08 21:21             ` Julia Lawall
2016-10-09 20:45               ` Nikolaus Rath
2016-10-10  4:49                 ` Julia Lawall
2016-10-10  4:54                 ` Julia Lawall
2016-10-10 15:56                   ` Nikolaus Rath
2016-10-10 18:45                     ` Nikolaus Rath
2016-10-10 19:45                       ` Julia Lawall
2016-10-10 21:27                         ` Nikolaus Rath
2016-10-10 21:33                           ` Julia Lawall
2016-10-10 23:00                             ` Nikolaus Rath
2016-10-11  6:51                               ` Julia Lawall
2016-10-12 15:08                                 ` Nikolaus Rath
2016-10-12 20:37                                   ` Julia Lawall
2016-10-05  5:51 ` SF Markus Elfring

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=57F52CBD.7020204@redhat.com \
    --to=mstefani@redhat.com \
    --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.