From: Julia Lawall <julia.lawall@inria.fr>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: cocci@inria.fr
Subject: Re: [cocci] Searching for repeated source code with SmPL?
Date: Sat, 11 May 2024 18:37:07 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2405111836340.14453@hadrien> (raw)
In-Reply-To: <3c953d7c-561d-4ba8-ae23-ffeb12840d02@web.de>
[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]
On Sat, 11 May 2024, Markus Elfring wrote:
> >> Why is no diff output generated by the software combination “Coccinelle 1.2-00008-g75525032”
> >> so far?
> >
> > Your semantic patch needs to be:
> >
> > @display@
> > @@
> > my_action(...);
> > <+... when any
> > *my_action(...);
> > ...+>
> >
> > Without that, a call to my_action is forbidden in the region matched by
> > the <+... ...+>. Because any kind of dot thing matches the shortest path
> > between what comes before and what comes after (here the end of the function).
>
> Thanks for this quick feedback.
>
> It seems that we expect different data processing also for the shown test case.
>
> The SmPL construct “<+... … ...+>” supports a search for code parts
> which occur at least once.
> Thus it seems that the specified search pattern needs be duplicated before
> if you would like to find code which should occur at least twice.
> I would appreciate if undesirable duplication of search patterns can be avoided here.
If you want to find code that occurs at least twice, isn't it most natural
to make a pattern that shows the thing occurring twice?
julia
next prev parent reply other threads:[~2024-05-11 16:37 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 10:08 [cocci] Searching for repeated source code with SmPL? Markus Elfring
2024-05-06 10:09 ` Julia Lawall
2024-05-06 11:03 ` Markus Elfring
2024-05-06 12:10 ` Markus Elfring
2024-05-06 12:16 ` Julia Lawall
2024-05-06 12:40 ` Markus Elfring
2024-05-11 15:36 ` Markus Elfring
2024-05-11 16:04 ` Julia Lawall
2024-05-11 16:35 ` Markus Elfring
2024-05-11 16:37 ` Julia Lawall [this message]
2024-05-11 17:02 ` Markus Elfring
2024-05-11 17:12 ` Julia Lawall
2024-05-11 17:21 ` Markus Elfring
2024-05-11 17:33 ` Julia Lawall
2024-05-12 6:48 ` Markus Elfring
2024-05-12 7:34 ` Julia Lawall
2024-05-12 8:01 ` Markus Elfring
2024-05-12 8:10 ` Julia Lawall
2024-05-12 8:33 ` Markus Elfring
2024-05-12 9:17 ` Julia Lawall
2024-05-12 9:30 ` Markus Elfring
2024-05-13 9:34 ` Markus Elfring
2024-05-12 11:24 ` Markus Elfring
2024-05-12 12:53 ` Julia Lawall
2024-05-12 13:07 ` Markus Elfring
2024-05-12 13:13 ` Julia Lawall
2024-05-12 13:22 ` Markus Elfring
2024-05-12 14:51 ` Markus Elfring
2024-05-12 14:57 ` Julia Lawall
2024-05-11 7:15 ` Markus Elfring
2024-05-22 8:20 ` Markus Elfring
2024-05-22 8:24 ` Julia Lawall
2024-05-22 8:44 ` Markus Elfring
2024-05-22 13:12 ` Markus Elfring
2024-05-22 15:34 ` Julia Lawall
2024-05-22 16:06 ` 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=alpine.DEB.2.22.394.2405111836340.14453@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 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.