From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Subject: Re: [cocci] Checking name space conflicts for SmPL script rules
Date: Thu, 25 Jan 2024 18:47:02 +0100 [thread overview]
Message-ID: <a487afb1-315e-4b90-9bac-591d422136f8@web.de> (raw)
In-Reply-To: <cd85b5cf-07f-a1f9-ba30-126045bfe15c@inria.fr>
>> Will the shown restriction be reconsidered?
>
> name is also a reserved word of Coccinelle, as in iterator name xxx;
I suggest to take another look at corresponding case distinctions.
I got the impression that the metavariable with the identifier “name” gets accepted
by this software for the first SmPL rule.
> Just pick some other name for your metavariable.
Can the avoidance of questionable name space conflicts become safer and more convenient
also for such a test case?
Regards,
Markus
prev parent reply other threads:[~2024-01-25 17:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 17:25 [cocci] Checking name space conflicts for SmPL script rules Markus Elfring
2024-01-25 17:29 ` Julia Lawall
2024-01-25 17:47 ` 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=a487afb1-315e-4b90-9bac-591d422136f8@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 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).