From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Subject: Re: [cocci] Fixing a parse error for a SmPL position variable constraint
Date: Wed, 14 Feb 2024 19:08:22 +0100 [thread overview]
Message-ID: <186ffd15-1234-4636-90db-fd9e1f9a5ed4@web.de> (raw)
In-Reply-To: <631c5dc8-285e-810-16b2-b41987e3e24d@inria.fr>
>> Markus_Elfring@Sonne:…/Projekte/Coccinelle/janitor> spatch --parse-cocci show_same_statements7w-20240214.cocci
>> …
>> Variable find.p2 in duplicated_code cannot be used as both a position and a constraint
>
> OK, I guess it is not allowed. Actually, the semantics of positive an
> negative uses of a position variable is quite different, so it seems that
> it is not allowed to use both at once.
Do we stumble on a target conflict here?
> But it should be possible to use two position variables at the original place.
Would you like to adjust affected software components accordingly?
Regards,
Markus
prev parent reply other threads:[~2024-02-14 18:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 13:08 [cocci] Fixing a parse error for a SmPL position variable constraint Markus Elfring
2024-02-13 20:45 ` Julia Lawall
2024-02-14 17:38 ` Markus Elfring
2024-02-14 17:49 ` Julia Lawall
2024-02-14 18:08 ` 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=186ffd15-1234-4636-90db-fd9e1f9a5ed4@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).