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: Sun, 12 May 2024 11:17:01 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2405121114580.6747@hadrien> (raw)
In-Reply-To: <3db2d501-d95d-40c7-8ac1-1ce8c3bd9340@web.de>
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
On Sun, 12 May 2024, Markus Elfring wrote:
> >>> Probably you should start with ... when != my_action(...) to be sure to
> >>> get the first one.
> >>
> >> I would expect that only the first function call should be matched by
> >> the initial SmPL search pattern (without an extra when constraint).
> >
> > Why would you expect that?
>
> I expect here that specific source code starts a known statement list.
Coccinelle takes a pattern expressed as a CTL formula and every node in
the control flow graph and tries to match the pattern at each node. The
matching at one node is independent of the matching at another node. If
there are conflicting matches that result in conflicting transformations,
then it generates an error message.
julia
>
>
> > Coccinelle looks through your function and matches the pattern anywhere it can.
>
> Can this software distinguish also better statement sequences accordingly?
>
>
> > The matches are independent of each other.
>
> * They can occasionally occur in different scopes.
>
> * Statement sequences (which include discussed repetitions) should be “interrupted”
> by other source code.
>
> Regards,
> Markus
>
next prev parent reply other threads:[~2024-05-12 9:18 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
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 [this message]
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.2405121114580.6747@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).