From: Markus Elfring <Markus.Elfring@web.de>
To: "Jérôme Glisse" <jglisse@redhat.com>
Cc: cocci@systeme.lip6.fr
Subject: Re: [Cocci] Add code after local variable declarations?
Date: Wed, 17 Apr 2019 18:42:23 +0200 [thread overview]
Message-ID: <857ac25c-4856-6284-6590-41b1ae44c8b5@web.de> (raw)
In-Reply-To: <20190417141429.GA3229@redhat.com>
> No i want to add some code to _all_ function that have a specific
> structure as one of their argument. Thus i match on the function
> parameter list for the struct i am interested in
This source code search approach is generally fine.
> and then after all the declaration i add a code snippet.
Our programmer eyes are trained for pattern recognition according to
such a software transformation.
* How many efforts would you like to invest into the development
for the automation of this refactoring (together with
the semantic patch language)?
* Would you like to determine the source code positions between
variable declaration (or definition) blocks and other statements safely?
* Will any additional constraints become relevant for this change attempt?
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
prev parent reply other threads:[~2019-04-17 16:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 22:11 [Cocci] Add code after local variable declarations ? Jerome Glisse
2019-04-17 5:14 ` Julia Lawall
2019-04-17 9:10 ` [Cocci] Add code after local variable declarations? Markus Elfring
2019-04-17 9:12 ` Julia Lawall
2019-04-17 9:42 ` Markus Elfring
2019-04-17 9:42 ` Markus Elfring
2019-04-17 14:14 ` [Cocci] Add code after local variable declarations ? Jerome Glisse
2019-04-17 14:32 ` Julia Lawall
2019-04-17 16:42 ` Markus Elfring [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=857ac25c-4856-6284-6590-41b1ae44c8b5@web.de \
--to=markus.elfring@web.de \
--cc=cocci@systeme.lip6.fr \
--cc=jglisse@redhat.com \
/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.