From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr
Subject: [cocci] Clarification for input data of scripted SmPL constraints
Date: Fri, 26 Jan 2024 13:50:19 +0100 [thread overview]
Message-ID: <8a6c0b00-c65b-4c83-afd9-4023132a4183@web.de> (raw)
Hello,
Some information is provided for the usage of ”scripted constraints”
by the means of the semantic patch language.
https://gitlab.inria.fr/coccinelle/coccinelle/-/blob/5fdb1a247d3374ac30a3e565b2cc5167aeefc4e5/docs/manual/cocci_syntax.tex#L582-605
https://github.com/coccinelle/coccinelle/blob/deb429dfae033e40aefc78729a585b00ae82808c/docs/manual/cocci_syntax.tex#L582-L605
They tend to depend on a single input parameter.
But how does the software situation look like if you would like to use contents
from multiple metavariables (which were hopefully matched in combination)
for advanced condition checks?
Regards,
Markus
next reply other threads:[~2024-01-26 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 12:50 Markus Elfring [this message]
2024-01-26 12:52 ` [cocci] Clarification for input data of scripted SmPL constraints Julia Lawall
2024-01-26 13:24 ` 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=8a6c0b00-c65b-4c83-afd9-4023132a4183@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).