From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr
Subject: [cocci] Handling of SmPL code exclusion specifications
Date: Thu, 20 Oct 2022 20:40:36 +0200 [thread overview]
Message-ID: <trinity-8d68c62b-e946-4ce2-b370-6555d910f65d-1666291236270@3c-app-webde-bap34> (raw)
Hello,
It was tried to clarify selected functionality from the Coccinelle software
several times through the years.
Unfortunately, it seems that especially the corresponding documentation
gets a questionable amount of system resources and development attention.
I hope that this sitation can be adjusted a bit by another clarification attempt.
I guess that the wording “code exclusion specifications” (according to
the semantic patch language) can be also helpful for some use cases.
https://gitlab.inria.fr/coccinelle/coccinelle/-/blob/86486f01bb7e1c2af326bba302c45cd54719445c/docs/manual/cocci_syntax.tex#L1021
https://github.com/coccinelle/coccinelle/blob/0406b12024e9943e26f255b0fffd1088ca0fdf27/docs/manual/cocci_syntax.tex#L1021
“…
Dots may be modified with a {\tt when} clause, indicating a pattern
that should not occur anywhere within the matched sequence.
…”
https://gitlab.inria.fr/coccinelle/coccinelle/-/blob/86486f01bb7e1c2af326bba302c45cd54719445c/docs/manual/cocci_syntax.tex#L1134
https://github.com/coccinelle/coccinelle/blob/0406b12024e9943e26f255b0fffd1088ca0fdf27/docs/manual/cocci_syntax.tex#L1134
grammar representation
This functionality has got special algorithmic properties.
Following source code (subsequent context information) needs to be checked
for the decision if something should be actually excluded (or not).
Such checking is usually repeated many times.
Thus code reviewers and software developers can occasionally become concerned
about corresponding run time characteristics.
Can the technology “computation tree logic” provide interesting hints
for this aspect?
Regards,
Markus
next reply other threads:[~2022-10-20 18:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 18:40 Markus Elfring [this message]
2022-10-21 14:30 ` [cocci] Explaining related information for computation tree logic? 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=trinity-8d68c62b-e946-4ce2-b370-6555d910f65d-1666291236270@3c-app-webde-bap34 \
--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).