From: Julia Lawall <julia.lawall@lip6.fr>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] Checking redundant variable initialisations with SmPL?
Date: Sun, 23 Jun 2019 15:13:20 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1906231511450.4961@hadrien> (raw)
In-Reply-To: <bf3a5ea0-3cda-4342-a6af-b27a4cc0295e@web.de>
On Sun, 23 Jun 2019, Markus Elfring wrote:
> > Try
> >
> > ... when any
> >
> > just before the final ). In some circumstaces the parser doesn't accept
> > an expression at the end of a sequence like you have here.
>
> Thanks for your quick response.
>
> The addition of such a SmPL ellipsis helps somehow.
> But I am still not pleased with the generated transformation result.
> So I am curious on how this software clarification will evolve further.
I am not pleased is not especially descriptive. If you have a question
about something, provide the semantic patch and the code on which you get
an undesired result.
I believe that you put a * on an assignment with var on the right hand
side, which at least doesn't correspond to my understanding of what you
are trying to do, so perhaps that is the problem.
julia
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-06-23 13:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 12:30 [Cocci] Checking redundant variable initialisations with SmPL? Markus Elfring
2019-06-21 20:52 ` Julia Lawall
2019-06-22 13:15 ` Markus Elfring
2019-06-22 13:19 ` Julia Lawall
2019-06-22 13:35 ` Markus Elfring
2019-06-22 13:58 ` Julia Lawall
2019-06-22 14:16 ` Markus Elfring
2019-06-23 7:48 ` Markus Elfring
2019-06-23 12:48 ` Markus Elfring
2019-06-23 12:48 ` Markus Elfring
2019-06-23 12:55 ` Julia Lawall
2019-06-23 13:05 ` Markus Elfring
2019-06-23 13:05 ` Markus Elfring
2019-06-23 13:13 ` Julia Lawall [this message]
2019-06-23 14:17 ` 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.1906231511450.4961@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