From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Replacing function definition with a macro
Date: Tue, 4 Aug 2015 19:09:16 +0200 [thread overview]
Message-ID: <55C0F1BC.2040206@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1508041029360.2327@hadrien>
> Coccinelle expects that each element in a parameter list will have the
> form type identifier.
Is the Coccinelle software still limited to some degree for the handling
of function parameters?
> In the case of name, you just have an identifier.
> I don't really see a solution.
How do you think about direct support for macro parameter lists?
Does anybody dare to contribute corresponding software development efforts?
Are there any more limitations to reconsider so that further post-processing
can be avoided for generated patches?
Regards,
Markus
prev parent reply other threads:[~2015-08-04 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 8:15 [Cocci] Replacing function definition with a macro Petr Malát
2015-08-04 8:31 ` Julia Lawall
2015-08-04 11:05 ` Petr Malát
2015-08-04 11:29 ` Julia Lawall
2015-08-04 17:09 ` SF 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=55C0F1BC.2040206@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