From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Cc: "Šerif Rami" <ramiserifpersia@gmail.com>
Subject: Re: [cocci] Reducing the scope for a selected variable with SmPL?
Date: Sat, 30 Aug 2025 14:28:12 +0200 [thread overview]
Message-ID: <0118a1aa-4327-488e-84d2-433cbf3ca2d1@web.de> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2508301423190.26590@hadrien>
…>>>> ... when != handshake_buf
>>>> when exists
…>> Do you propose to generalise such a source code transformation approach
>> any further?
>
> I don't propose to do anything. If you want to do something like this,
> you have to check that handshake_buf doesn't occur on other paths.
Do you find the mentioned SmPL code exclusion specification insufficient
so far?
Regards,
Markus
prev parent reply other threads:[~2025-08-30 12:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 6:30 [cocci] Reducing the scope for a selected variable with SmPL? Markus Elfring
2025-08-22 7:13 ` Markus Elfring
2025-08-23 6:08 ` Markus Elfring
2025-08-23 9:54 ` Julia Lawall
2025-08-23 11:26 ` Markus Elfring
2025-08-23 11:46 ` Julia Lawall
2025-08-30 11:36 ` Markus Elfring
2025-08-30 12:01 ` Julia Lawall
2025-08-30 12:20 ` Markus Elfring
2025-08-30 12:23 ` Julia Lawall
2025-08-30 12:28 ` Markus Elfring [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=0118a1aa-4327-488e-84d2-433cbf3ca2d1@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=julia.lawall@inria.fr \
--cc=ramiserifpersia@gmail.com \
/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