From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr
Subject: Re: [cocci] Improving handling of position information for SmPL?
Date: Mon, 29 Sep 2025 16:18:44 +0200 [thread overview]
Message-ID: <58be2182-270a-4d2b-93b3-35e737d68841@web.de> (raw)
In-Reply-To: <61f326c5-7c60-4390-bcb7-20707fc68b6f@web.de>
> Some data processing results can be observed then also according to
> the software combination “Coccinelle 1.3.0”.
It seems that the printout of generated computation tree logic terms
might not be so helpful so far.
Thus I imagine that another development idea can influence software evolution
in desirable directions.
SmPL variables are available to be filled with data.
They can get useful contents
* after a source code search was performed
or
* values were set by a supported scripting interface.
Position metavariables have got special properties.
They can be connected to selected source code places.
I am looking for further clarifications also according to corresponding
implementation details:
1. It can be determined if position information is actually reused.
May any additional variables be omitted from data processing?
2. If position data are inherited, they are attached to found items.
I assume that these items do eventually not need to be researched again
because code places were marked already.
Would position metavariables suppress any data evaluation for companion items?
Regards,
Markus
prev parent reply other threads:[~2025-09-29 14:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 9:22 [cocci] Improving handling of position information for SmPL? Markus Elfring
2025-09-29 14:18 ` Markus Elfring [this message]
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=58be2182-270a-4d2b-93b3-35e737d68841@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).