From: Julia Lawall <julia.lawall@lip6.fr>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] Challenges around asterisk usage in SmPL code
Date: Sun, 25 Aug 2019 15:48:20 +0800 (CST) [thread overview]
Message-ID: <alpine.DEB.2.21.1908251547420.2283@hadrien> (raw)
In-Reply-To: <661aa3dc-3514-3d75-eb3a-9e46843fd02d@web.de>
[-- Attachment #1: Type: text/plain, Size: 866 bytes --]
On Sun, 25 Aug 2019, Markus Elfring wrote:
> >> @assignment@
> >> expression x, y;
> >> @@
> >> * y = ... *(x) ...;
> >
> > This doesn’t do what you think.
>
> This might be.
>
>
> > It matches a series of statements, I’m not even completely sure how.
>
> Such a feedback is also interesting.
> My imaginations evolved in other directions.
>
>
> > There can’t be a series of statements before an else.
>
> This view can depend on the interpretation around the handling of compound statements,
> can't it?
>
>
> > You want <+... ...+>
>
> Does this SmPL construct help to restrict a source code search element
> (while using SmPL ellipses) to a single statement for the shown analysis example?
Yes.
>
> Will the support for unary operations need any further development considerations?
No, the precedence should be ok as is.
julia
> Regards,
> Markus
>
[-- Attachment #2: Type: text/plain, Size: 136 bytes --]
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-08-25 7:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-24 17:33 [Cocci] Challenges around asterisk usage in SmPL code Markus Elfring
[not found] ` <2AE15A09-F219-43DC-81A9-73C13CFC0753@lip6.fr>
2019-08-25 7:40 ` Markus Elfring
2019-08-25 7:48 ` Julia Lawall [this message]
2019-08-25 8:13 ` Markus Elfring
2019-08-25 8:30 ` [Cocci] Searching for unary operations with SmPL Markus Elfring
2019-08-25 9:11 ` [Cocci] Challenges around asterisk usage in SmPL code Markus Elfring
2019-08-25 9:45 ` Julia Lawall
2019-08-25 10:22 ` Markus Elfring
2019-08-25 13:13 ` [Cocci] Checking information from “--parse-cocci” Markus Elfring
[not found] ` <alpine.DEB.2.21.1908252118210.2801@hadrien>
2019-08-25 13:45 ` Markus Elfring
[not found] ` <alpine.DEB.2.21.1908252209170.3506@hadrien>
2019-08-25 14:19 ` Markus Elfring
2019-08-25 17:34 ` [Cocci] Challenges around asterisk usage in SmPL code Markus Elfring
2019-08-26 17:26 ` [Cocci] Checking null pointer handling with SmPL Markus Elfring
2019-08-27 0:58 ` Julia Lawall
2019-08-28 11:50 ` 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.1908251547420.2283@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).