From: Julia Lawall <julia.lawall@inria.fr>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Subject: Re: [cocci] Searching for code within block by SmPL ellipsis?
Date: Sun, 25 Feb 2024 22:21:22 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2402252220350.3333@hadrien> (raw)
In-Reply-To: <3d07b481-066e-49b1-96c0-e63391975ad8@web.de>
On Sun, 25 Feb 2024, Markus Elfring wrote:
> > The fact that no * is detected does seem like a problem.
>
> Will variations of a source code search approach (like the following)
> including the usage of a combination of SmPL asterisk and ellipsis
> between curly brackets become supported?
>
> @display@
> @@
> {
> * ...
> ;
> }
Thank you for the smaller example.
julia
prev parent reply other threads:[~2024-02-25 21:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 9:05 [cocci] Detecting misused expressions with SmPL? Markus Elfring
2024-02-22 13:22 ` Julia Lawall
2024-02-22 14:27 ` Markus Elfring
2024-02-22 15:43 ` Markus Elfring
2024-02-22 17:35 ` Markus Elfring
2024-02-25 15:33 ` [cocci] Searching for code within block by SmPL ellipsis? Markus Elfring
2024-02-25 21:21 ` Julia Lawall [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=alpine.DEB.2.22.394.2402252220350.3333@hadrien \
--to=julia.lawall@inria.fr \
--cc=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).