From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Subject: Re: [cocci] Too limited support for SmPL statement lists?
Date: Mon, 9 Mar 2026 07:07:42 +0100 [thread overview]
Message-ID: <c21af64b-dfd1-471d-b9bf-3f1c91b5bdfd@web.de> (raw)
In-Reply-To: <aa67fc7a-62b7-b6fd-d860-fd73623e6b77@inria.fr>
> A statement list metavariable only matches the code starting right after a {.
> It can't start in random places. …
I got the impression then that the supported functionality is so limited for
the metavariable type “statement list” so far.
It seems that it is unlikely to be usable besides discussed test cases.
Statements are often mixed with variable declarations and definitions.
Regards,
Markus
prev parent reply other threads:[~2026-03-09 6:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-01 13:50 [cocci] Reproducing a known patch with SmPL? Markus Elfring
2026-03-01 16:51 ` Markus Elfring
2026-03-02 11:15 ` Markus Elfring
2026-03-07 10:15 ` [cocci] Reconsidering source code search challenges for nested compound statements Markus Elfring
2026-03-08 13:00 ` Markus Elfring
2026-03-08 13:24 ` Julia Lawall
2026-03-08 14:05 ` Markus Elfring
2026-03-08 14:55 ` Markus Elfring
2026-03-08 15:24 ` Julia Lawall
2026-03-08 16:08 ` Markus Elfring
2026-03-08 16:53 ` Julia Lawall
2026-03-08 17:35 ` Markus Elfring
2026-03-08 17:46 ` Julia Lawall
2026-03-08 17:52 ` Markus Elfring
2026-03-08 18:01 ` Julia Lawall
2026-03-08 18:11 ` Markus Elfring
2026-03-08 18:20 ` Julia Lawall
2026-03-08 18:30 ` Markus Elfring
2026-03-08 19:54 ` Markus Elfring
2026-03-09 6:07 ` 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=c21af64b-dfd1-471d-b9bf-3f1c91b5bdfd@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