From: Nikolaus@rath.org (Nikolaus Rath)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Replacing one (specific!) type with another
Date: Wed, 05 Oct 2016 09:09:22 -0700 [thread overview]
Message-ID: <87shsa7p71.fsf@thinkpad.rath.org> (raw)
In-Reply-To: <alpine.DEB.2.10.1610050744460.3061@hadrien> (Julia Lawall's message of "Wed, 5 Oct 2016 07:45:27 +0200 (CEST)")
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).
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).
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
?Time flies like an arrow, fruit flies like a Banana.?
next prev parent reply other threads:[~2016-10-05 16:09 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 [this message]
2016-10-05 16:39 ` Michael Stefaniuc
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=87shsa7p71.fsf@thinkpad.rath.org \
--to=nikolaus@rath.org \
--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.