From: Markus Elfring <Markus.Elfring@web.de>
To: Coccinelle <cocci@systeme.lip6.fr>
Subject: [Cocci] Splitting a source code search specification from a SmPL rule into more rules?
Date: Wed, 6 Mar 2019 10:40:36 +0100 [thread overview]
Message-ID: <a92e39ec-4daa-0101-553e-21ca743c2df0@web.de> (raw)
Hello,
The semantic patch language supports also to put longer code into SmPL rules.
It might look convenient and appropriate to specify such code for a single
SmPL rule. But it can happen also that you would like to reduce source code
search efforts and present meaningful analysis reports.
Example:
It can be specified that a specific function call should be found as
a precondition.
A corresponding hit can be additionally indicated in a variable for
an embedded programming language (like OCaml or Python) in a subsequent script
rule so that this variable can influence a message construction in a final rule.
How are the chances to restart (or continue) the code search after found places
(without repeating SmPL code from the precondition)?
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
reply other threads:[~2019-03-06 9:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=a92e39ec-4daa-0101-553e-21ca743c2df0@web.de \
--to=markus.elfring@web.de \
--cc=cocci@systeme.lip6.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 NNTP newsgroup(s).