From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Subject: Re: [cocci] Supporting expression fragments with SmPL dot variants?
Date: Sun, 27 Jul 2025 16:24:43 +0200 [thread overview]
Message-ID: <ca8b22e3-7ccc-4e33-9938-9035d259cec6@web.de> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2507271618550.3493@hadrien>
>> @display@
>> expression x, y;
>> @@
>> *(1 * x) /
>> ...
>> *(2 * y) /
>> <+...
>> *(4 * x) /
>> ...+>
>
> You have to make a real expression.
I hope that this software limitation can reconsidered better.
> What you show is not a real expression.
This is obvious.
Can it be detected anyhow that corresponding parts are occasionally repeated?
Regards,
Markus
prev parent reply other threads:[~2025-07-27 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-27 13:36 [cocci] Supporting expression fragments with SmPL dot variants? Markus Elfring
2025-07-27 14:19 ` Julia Lawall
2025-07-27 14:24 ` 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=ca8b22e3-7ccc-4e33-9938-9035d259cec6@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).