From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Subject: Re: [cocci] Analysis challenges with SmPL for pass-through functions?
Date: Sun, 19 Oct 2025 16:37:43 +0200 [thread overview]
Message-ID: <769428aa-9801-4805-bfc3-cd789f7541d1@web.de> (raw)
In-Reply-To: <e5b2ceef-31a0-a54-dd74-c4dcdfcba5a@inria.fr>
>>> If you don't want them to match the same thing, then you need to use a
>>> disjunction. In the first branch, the same metavariable should be used
>>> twice, and then in the second branch there would be the two different
>>> metavariables. The match should only be indicated for the second branch.
>> Does such a solution approach indicate a data processing requirement
>> for multiple source code searches so that anything would be excluded finally?
> No idea what this means.
How many searches would need to be performed for the evaluation of
SmPL disjunction elements?
Regards,
Markus
next prev parent reply other threads:[~2025-10-19 14:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-19 14:00 [cocci] Analysis challenges with SmPL for pass-through functions? Markus Elfring
2025-10-19 14:10 ` Julia Lawall
2025-10-19 14:25 ` Markus Elfring
2025-10-19 14:30 ` Julia Lawall
2025-10-19 14:37 ` Markus Elfring [this message]
2025-10-19 14:40 ` Julia Lawall
2025-10-19 14:50 ` Markus Elfring
2025-10-21 6:16 ` Markus Elfring
2025-10-21 9:12 ` Julia Lawall
2025-10-21 9:40 ` Markus Elfring
2025-10-24 19:03 ` [cocci] Terminology evolution for SmPL? Markus Elfring
2025-10-22 9:20 ` [cocci] Analysis challenges with SmPL for pass-through functions? 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=769428aa-9801-4805-bfc3-cd789f7541d1@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=julia.lawall@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).