From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr
Subject: [cocci] Evolution for data reuse with generic SmPL metavariable types?
Date: Sat, 28 Mar 2026 13:56:19 +0100 [thread overview]
Message-ID: <815c88e4-44bd-4a9e-b25c-324e953decae@web.de> (raw)
Hello!
Metavariables are supported to some degree.
https://gitlab.inria.fr/coccinelle/coccinelle/-/blob/03a1af0a3316ddfc2b54d827b8b9627a841c85c9/docs/manual/cocci_syntax.tex#L209-288
I find that their types can be distinguished by corresponding properties.
1. generic
2. number of items (which can be matched)
Examples:
* statement
* declaration
A declaration can contain the following elements.
+ variable type
+ identifier
+ attributes
+ comments
Thus it would occasionally be helpful if such contents can be reused directly.
But there are corresponding data processing constraints involved.
These data would only become usable after detection according to a (compound)
metavariable type.
How will development interests evolve to improve programming interfaces accordingly?
Regards,
Markus
next reply other threads:[~2026-03-28 12:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-28 12:56 Markus Elfring [this message]
2026-04-03 8:00 ` [cocci] Evolution for data reuse with generic SmPL metavariable types? 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=815c88e4-44bd-4a9e-b25c-324e953decae@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.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