From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr
Subject: [cocci] Passing code replacements by APIs (for SmPL)?
Date: Sun, 22 Jun 2025 09:30:24 +0200 [thread overview]
Message-ID: <2dc257b4-d310-47dd-90ea-9b081727be2a@web.de> (raw)
Hello,
The semantic patch language supports the specification of source code replacements.
Such replacements are specified within SmPL rules. The evaluation of several
SmPL rules would trigger corresponding software run time consequences.
Thus it can occasionally be preferred to combine some data processing selections
into SmPL disjunctions.
Desirable source code adjustments can also be generated into SmPL script variants.
I imagine that it can occasionally be nicer to avoid such script generation
because the Coccinelle software can benefit also from source file analyses.
How will the chances evolve to extend application programming interfaces accordingly?
https://gitlab.inria.fr/coccinelle/coccinelle/-/blob/c52d87d02775dea45d51a3c9440646525e4b5f29/docs/Coccilib.3cocci#L26
https://gitlab.inria.fr/coccinelle/coccinelle/-/blob/c52d87d02775dea45d51a3c9440646525e4b5f29/python/python_documentation.md
Regards,
Markus
next reply other threads:[~2025-06-22 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-22 7:30 Markus Elfring [this message]
2025-06-23 8:05 ` [cocci] Passing code replacements by APIs (for SmPL)? Markus Elfring
2025-06-26 11:18 ` 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=2dc257b4-d310-47dd-90ea-9b081727be2a@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).