From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Subject: Re: [cocci] Using statement list combinations?
Date: Thu, 3 Jul 2025 12:28:09 +0200 [thread overview]
Message-ID: <7a1ae793-7f9b-4ec7-9cc7-db176207369a@web.de> (raw)
In-Reply-To: <44735e62-2ed6-730-6ab3-b2251d8b6723@inria.fr>
>> Would you find an SmPL code variant (like the following) more reasonable?
>>
>> @display@
>> statement header, footer;
>> statement list sl;
>> @@
>> *header { sl } footer
>
> I don't know what you expect it to match.
Such a source code search approach is very generic.
I am curious how often this code pattern could be found finally.
Regards,
Markus
next prev parent reply other threads:[~2025-07-03 10:28 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 ` [cocci] Search challenges for “statement lists”? Markus Elfring
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 [this message]
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=7a1ae793-7f9b-4ec7-9cc7-db176207369a@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.