From: johannes@sipsolutions.net (Johannes Berg)
To: cocci@systeme.lip6.fr
Subject: [Cocci] modifying initializers with spatch?
Date: Fri, 27 Jan 2017 17:13:04 +0100 [thread overview]
Message-ID: <1485533584.14579.1.camel@sipsolutions.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1701271408210.3117@hadrien>
On Fri, 2017-01-27 at 14:11 +0100, Julia Lawall wrote:
> > Out of curiosity: will it require some form of "..." to match
> > something inside now?
>
> No.
Ok.
> It considers that the rule writer has no knowledge or control of the
> field names that are provided or the order in which they appear, so
> you can specify any subset of them.??You only need ... when you want
> to add a new one at the beginning or at the end of the
> structure.??The ... lets you specify beginning or end.
Interesting. I thought I needed the ... at the end, but that may have
been a case of "let's see if I need both - doesn't work - remove one -
ok works now" :)
> I want to allow you to remove the {} only when all of the field
> initializations are also removed.??Some work though is required.
That'd make sense.
I'm very grateful for this. I'm dealing with an awful compiler that
emits stupid code for C99 initializers, so I'm thinking of using what
we were discussing here to remove them all at build time. I'm going to
be travelling (again) next week, but will give it a try later.
Thanks a lot!
johannes
prev parent reply other threads:[~2017-01-27 16:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 12:28 [Cocci] modifying initializers with spatch? Johannes Berg
2017-01-26 13:17 ` Julia Lawall
2017-01-26 13:32 ` Johannes Berg
2017-01-26 14:20 ` Julia Lawall
2017-01-26 14:28 ` Johannes Berg
2017-01-26 15:47 ` Julia Lawall
2017-01-26 15:52 ` Johannes Berg
2017-01-26 15:57 ` Julia Lawall
2017-01-27 21:43 ` Johannes Berg
2017-01-27 21:52 ` Julia Lawall
2017-01-27 22:03 ` Johannes Berg
2017-01-27 22:09 ` Julia Lawall
2017-01-27 22:23 ` Johannes Berg
2017-01-27 23:02 ` Johannes Berg
2017-01-27 23:20 ` Johannes Berg
2017-01-28 6:47 ` Julia Lawall
2017-01-28 8:20 ` Johannes Berg
2017-01-27 7:09 ` Julia Lawall
2017-01-27 8:55 ` Johannes Berg
2017-01-27 13:11 ` Julia Lawall
2017-01-27 16:13 ` Johannes Berg [this message]
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=1485533584.14579.1.camel@sipsolutions.net \
--to=johannes@sipsolutions.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.