From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr
Subject: [cocci] Supporting expression fragments with SmPL dot variants?
Date: Sun, 27 Jul 2025 15:36:47 +0200 [thread overview]
Message-ID: <67e35fac-d223-4067-882b-a632a57c792c@web.de> (raw)
Hello,
I would like to try something out with another script for the semantic patch language.
@display@
expression x, y;
@@
*(1 * x) /
...
*(2 * y) /
<+...
*(4 * x) /
...+>
Unfortunately, I stumbled on the following test result then.
Markus_Elfring@Sonne:…/Projekte/Coccinelle/janitor> /usr/bin/spatch --parse-cocci show_questionable_evaluation_order1.cocci
…
minus: parse error:
File "show_questionable_evaluation_order1.cocci", line 9, column 1, charpos = 76
around = '...+>',
whole content = ...+>
Can the data processing be extended anyhow also for expression fragments?
Regards,
Markus
next reply other threads:[~2025-07-27 13:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-27 13:36 Markus Elfring [this message]
2025-07-27 14:19 ` [cocci] Supporting expression fragments with SmPL dot variants? Julia Lawall
2025-07-27 14:24 ` 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=67e35fac-d223-4067-882b-a632a57c792c@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).