From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] remove typedefs from struct
Date: Sun, 15 Feb 2015 18:13:53 +0100 [thread overview]
Message-ID: <54E0D3D1.9070608@users.sourceforge.net> (raw)
In-Reply-To: <2bb2afa2a75f464b900af8506ddc84dd@BN1BFFO11FD029.protection.gbl>
> /// Convert typdefed structs to structs
>
> @ rule1 @
> identifier i;
> type t;
> @@
> -typedef struct i {
> +struct i {
> ...
> - }t;
> + };
How do you think about a bit more fine-tuning for your SmPL approach?
...
}
-t
;
Is it sufficient to express the desired deletion at this place?
Regards,
Markus
next prev parent reply other threads:[~2015-02-15 17:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-14 18:29 [Cocci] remove typedefs from struct Sören Brinkmann
2015-02-14 18:56 ` Julia Lawall
2015-02-15 1:22 ` Sören Brinkmann
2015-02-15 5:54 ` Julia Lawall
2015-02-15 9:38 ` Julia Lawall
2015-02-15 21:05 ` Sören Brinkmann
2015-02-15 21:16 ` Julia Lawall
2015-02-15 21:31 ` Sören Brinkmann
2015-02-15 21:41 ` Julia Lawall
2015-02-15 21:53 ` Sören Brinkmann
2015-02-15 21:56 ` Julia Lawall
2015-02-16 9:00 ` Sören Brinkmann
2015-02-16 9:10 ` Julia Lawall
2015-02-16 15:59 ` Sören Brinkmann
2015-02-17 6:56 ` Julia Lawall
2015-02-17 19:42 ` Sören Brinkmann
2015-02-17 20:31 ` Julia Lawall
2015-02-18 0:50 ` Sören Brinkmann
2015-02-18 21:44 ` Julia Lawall
2015-02-19 9:08 ` [Cocci] Finding several type qualifiers with SmPL? SF Markus Elfring
2015-02-19 16:47 ` Sören Brinkmann
2015-02-19 16:54 ` Julia Lawall
2015-02-19 18:55 ` SF Markus Elfring
2015-02-19 18:30 ` SF Markus Elfring
2015-02-15 17:13 ` SF Markus Elfring [this message]
2015-02-15 17:32 ` [Cocci] remove typedefs from struct Julia Lawall
2015-02-15 20:15 ` Sören Brinkmann
2015-02-16 4:31 ` Sören Brinkmann
2015-02-16 6:19 ` Julia Lawall
2015-02-16 7:51 ` Sören Brinkmann
2015-02-16 8:10 ` 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=54E0D3D1.9070608@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox