From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Subject: Re: [cocci] Search challenges for “statement lists”?
Date: Wed, 2 Jul 2025 11:11:47 +0200 [thread overview]
Message-ID: <166b2e55-fe21-4e0f-856f-1628d7d06c9e@web.de> (raw)
In-Reply-To: <8a69338-c049-cce1-2d66-a9607c175270@inria.fr>
> You can write { sl }.
Such a source code search pattern can occasionally be helpful.
https://gitlab.inria.fr/coccinelle/coccinelle/-/blob/b00c5adb1a485321c88450bdaa9e0d9ff93123dc/docs/manual/cocci_syntax.tex#L348-350
> You can't write S1 sl S2.
Which software constraints would hinder the application of such a metavariable combination
so far?
> There exists no representation of a list of statements that sl can bind to.
Is there a need to clarify further possible software extensions?
Regards,
Markus
next prev parent reply other threads:[~2025-07-02 9:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 8:01 [cocci] Searching function implementations with more than a single return? Markus Elfring
2025-07-01 11:54 ` [cocci] Searching function implementations with variable declarations and statements? Markus Elfring
2025-07-01 12:09 ` Julia Lawall
2025-07-01 12:26 ` Markus Elfring
2025-07-01 12:29 ` Julia Lawall
2025-07-01 12:00 ` Markus Elfring
2025-07-01 12:42 ` Markus Elfring
2025-07-01 13:41 ` Julia Lawall
2025-07-01 13:55 ` Markus Elfring
2025-07-01 14:01 ` Julia Lawall
2025-07-01 13:01 ` [cocci] Searching function implementations with more than a single return? Markus Elfring
2025-07-01 13:40 ` Julia Lawall
2025-07-01 13:50 ` Markus Elfring
2025-07-01 13:59 ` Julia Lawall
2025-07-01 14:06 ` Markus Elfring
2025-07-01 15:17 ` Julia Lawall
2025-07-01 18:00 ` Markus Elfring
2025-07-02 9:11 ` Markus Elfring [this message]
2025-07-03 10:00 ` [cocci] Using statement list combinations? Markus Elfring
2025-07-03 10:23 ` Julia Lawall
2025-07-03 10:28 ` Markus Elfring
2025-07-03 11:54 ` Julia Lawall
2025-07-03 13:25 ` 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=166b2e55-fe21-4e0f-856f-1628d7d06c9e@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