From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr
Cc: kernel-janitors@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: [cocci] [RFC] Choosing “semantics” better for SmPL script parts?
Date: Sun, 24 Aug 2025 14:40:35 +0200 [thread overview]
Message-ID: <574a6fa0-00a0-43c2-8e66-cc6443f5cfd4@web.de> (raw)
Hello,
A bit of information is provided about special “semantics” (also in the manual
for the semantic patch language).
https://gitlab.inria.fr/coccinelle/coccinelle/-/blob/face14907c0791b93397d5788d2a94c7c6a4b886/docs/manual/cocci_syntax.tex#L1007-1014
Usage possibilities are indicated for the key words “exists” and “forall”.
* Would any more software users like to discuss and clarify safer applications
of these system configuration parameters?
* Would you be looking for better “connections” according to computation tree
logic (or linear temporal logic) variations?
Regards,
Markus
next reply other threads:[~2025-08-24 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-24 12:40 Markus Elfring [this message]
2025-08-25 7:30 ` [cocci] [RFC] Choosing “semantics” better for SmPL script parts? Markus Elfring
2025-08-25 13:23 ` Julia Lawall
2025-08-25 15:17 ` Markus Elfring
2025-08-26 7:30 ` 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=574a6fa0-00a0-43c2-8e66-cc6443f5cfd4@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).