From: Markus Elfring <Markus.Elfring@web.de>
To: Anon Anonson <anon@chud.cyou>
Cc: cocci@inria.fr
Subject: Re: [cocci] Renaming identifiers with SmPL
Date: Tue, 16 Sep 2025 10:00:23 +0200 [thread overview]
Message-ID: <823b575c-505d-44bc-91cf-f424f9b2e14f@web.de> (raw)
In-Reply-To: <d04274ea-7bff-4c63-8fc6-55a19ab45b55@chud.cyou>
> Given the following script:
> @ rn_dec @
> type T;
> identifier I = i;
I suggest to reconsider the need for such an SmPL constraint.
> @@
>
> - T I
> + T b
> ;
T
-old
+new
;
…> However, I would expect the declaration inside the 'for' to be replaced too.
Would you like to support any restrictions where anything should not be renamed accidentally?
Regards,
Markus
next prev parent reply other threads:[~2025-09-16 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-14 11:47 [cocci] Possible bug Anon Anonson
2025-09-15 21:37 ` Julia Lawall
2025-10-19 19:34 ` Anon Anonson
2025-09-16 8:00 ` Markus Elfring [this message]
2025-09-16 8:25 ` [cocci] Renaming identifiers with SmPL? 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=823b575c-505d-44bc-91cf-f424f9b2e14f@web.de \
--to=markus.elfring@web.de \
--cc=anon@chud.cyou \
--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).