From: Julia Lawall <julia.lawall@lip6.fr>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] Using the same replacement for different source code
Date: Thu, 14 Nov 2019 08:14:42 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.21.1911140813570.2239@hadrien> (raw)
In-Reply-To: <42fd0ee0-d4b7-5f30-2896-57bd10900be7@web.de>
On Thu, 14 Nov 2019, Markus Elfring wrote:
> >> @replacement@
> >> binary operator bo = { +, * };
> >> expression x, y;
> >> @@
> >> +compute(
> >> x
> >> - bo
> >> + ,
> >> y
> >> + )
> >
> > I can't figure out what this is an example of?
>
> It shows just a possible transformation specification where a SmPL constraint
> is applied instead of a related SmPL disjunction.
>
> See also:
> https://lore.kernel.org/cocci/59c2f820-af2b-030f-3f8e-1dc0fd23f4ba@web.de/
> https://systeme.lip6.fr/pipermail/cocci/2019-November/006582.html
>
>
> > Does this work or not?
>
> This bit of SmPL code gets parsed by the Coccinelle software as expected.
>
> Does it demonstrate similar development opportunities?
OK, so we have an example that works. What doesn't work that you are
asking about?
julia
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-11-14 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 12:15 [Cocci] Using the same replacement for different source code Markus Elfring
2019-11-12 13:24 ` Julia Lawall
2019-11-14 7:12 ` Markus Elfring
2019-11-14 15:35 ` Julia Lawall
2019-11-14 16:12 ` Markus Elfring
2019-11-14 16:14 ` Julia Lawall [this message]
2019-11-14 16:34 ` Markus Elfring
-- strict thread matches above, loose matches on Subject: below --
2019-11-12 12:15 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=alpine.DEB.2.21.1911140813570.2239@hadrien \
--to=julia.lawall@lip6.fr \
--cc=Markus.Elfring@web.de \
--cc=cocci@systeme.lip6.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 NNTP newsgroup(s).