From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr
Subject: [cocci] Checking name space conflicts for SmPL script rules
Date: Thu, 25 Jan 2024 18:25:57 +0100 [thread overview]
Message-ID: <ec692ed7-01e5-493b-95b6-75ca7a59fb1b@web.de> (raw)
Hello,
I am trying the following tiny script variant for the semantic patch language out
also together with the software combination “Coccinelle 1.1.1-00630-gdeb429df”.
@search@
identifier name;
@@
name(...);
@script:python selection@
id << search.name;
@@
if id == "Test":
cocci.include_match(False)
Markus_Elfring@Sonne:…/Projekte/Coccinelle/Probe> spatch --parse-cocci test-name_space_conflict-20240125.cocci
…
scriptmeta: parse error:
File "test-name_space_conflict-20240125.cocci", line 7, column 13, charpos = 81
around = 'name',
whole content = id << search.name;
Now I wonder how this software behaviour would fit to the documentation.
https://gitlab.inria.fr/coccinelle/coccinelle/-/blob/5fdb1a247d3374ac30a3e565b2cc5167aeefc4e5/docs/manual/cocci_syntax.tex#L87
Will the shown restriction be reconsidered?
Regards,
Markus
next reply other threads:[~2024-01-25 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 17:25 Markus Elfring [this message]
2024-01-25 17:29 ` [cocci] Checking name space conflicts for SmPL script rules Julia Lawall
2024-01-25 17:47 ` 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=ec692ed7-01e5-493b-95b6-75ca7a59fb1b@web.de \
--to=markus.elfring@web.de \
--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).