From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Cc: Michele Martone <michelemartone@users.sourceforge.net>
Subject: Re: [cocci] Searching for C++ delete expressions (with SmPL)?
Date: Sat, 9 Aug 2025 09:01:22 +0200 [thread overview]
Message-ID: <2e148620-fa5f-43cd-b17f-edbc292d0bf5@web.de> (raw)
In-Reply-To: <0618c7d1-e0b8-459d-a94e-06446e26593e@web.de>
> Will another SmPL script example trigger further collateral evolution?
Would you be looking for SmPL script variations which can handle known
C++ source code transformation patterns to some degree?
* https://clang.llvm.org/extra/clang-tidy/checks/readability/delete-null-pointer.html
* https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#r11-avoid-calling-new-and-delete-explicitly
Regards,
Markus
prev parent reply other threads:[~2025-08-09 7:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 8:00 [cocci] Searching for C++ delete expressions (with SmPL)? Markus Elfring
2025-08-08 8:04 ` Julia Lawall
2025-08-08 8:15 ` Markus Elfring
2025-08-08 8:29 ` Julia Lawall
2025-08-08 9:01 ` Markus Elfring
2025-08-09 6:44 ` Markus Elfring
2025-08-09 7:01 ` 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=2e148620-fa5f-43cd-b17f-edbc292d0bf5@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=julia.lawall@inria.fr \
--cc=michelemartone@users.sourceforge.net \
/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