From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr
Subject: [cocci] Checking a parse error for detailed SmPL rule properties
Date: Wed, 24 Jan 2024 16:40:28 +0100 [thread overview]
Message-ID: <4604ee8e-a876-4545-b0cb-e4fba2e187a2@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”.
virtual report, org
@or depends on org || report disable sizeof_type_expr@
position p;
@@
my_action@p(...)
Markus_Elfring@Sonne:…/Projekte/Coccinelle/Probe> spatch --parse-cocci or-test2-20240124.cocci
…
rule name: parse error:
File "or-test2-20240124.cocci", line 3, column 1, charpos = 22
around = 'or',
whole content = @or depends on org || report disable sizeof_type_expr@
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
May SmPL rule identifiers be chosen freely?
Regards,
Markus
next reply other threads:[~2024-01-24 15:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 15:40 Markus Elfring [this message]
2024-01-24 17:22 ` [cocci] Checking a parse error for detailed SmPL rule properties Julia Lawall
2024-01-24 17:52 ` Markus Elfring
2024-01-24 17:56 ` Julia Lawall
2024-01-24 18:02 ` Markus Elfring
2024-01-24 18:08 ` Julia Lawall
2024-01-24 18:12 ` Markus Elfring
2024-01-24 20:26 ` Julia Lawall
2024-01-24 21:06 ` 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=4604ee8e-a876-4545-b0cb-e4fba2e187a2@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).