From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Subject: Re: [cocci] Searching for repeated source code with SmPL?
Date: Sun, 12 May 2024 10:01:05 +0200 [thread overview]
Message-ID: <bac7cb07-aac0-4fb2-b524-3f53f8109a68@web.de> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2405120932360.6747@hadrien>
>> Can the data processing be improved anyhow?
>
> The current semantic pach allows the first my_action to match anywhere,
> including the second my_action, third, etc. So if you have changes in both,
> then there will be contradictory changes to the code.
I suggest to reconsider such information in more detail according to
the presented transformation approach.
> 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).
Should subsequent repeated calls be taken into account only for the shown
deletion attempt?
Regards,
Markus
next prev parent reply other threads:[~2024-05-12 8:01 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 [this message]
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=bac7cb07-aac0-4fb2-b524-3f53f8109a68@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.