cocci.inria.fr archive mirror
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: cocci@systeme.lip6.fr
Subject: Re: [Cocci] Add code after local variable declarations?
Date: Wed, 17 Apr 2019 11:12:17 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1904171111410.2612@hadrien> (raw)
In-Reply-To: <2f0588f4-07fd-cf8e-1a57-e5fb66b0ca5b@web.de>



On Wed, 17 Apr 2019, Markus Elfring wrote:

> > @@
> > statement S,S1;
> > @@
> >
> > foo(...) {
> >   ... when != S
> > + added code
> >   S1
> >   ...
> > }
> >
> > A declaration doesn't match S.
>
> Can this information trigger additional considerations for the handling
> of variable definitions?
>
> Would you like to add any source code only after a variable declaration

Coccinelle doesn't allow this.  It has no way of knowing whether other
declarations come afterwards, and in the Linux kernel it is not allowed to
mix statements and declarations.

julia

> (or definition) block?
>
> Regards,
> Markus
>
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci

  reply	other threads:[~2019-04-17  9:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16 22:11 [Cocci] Add code after local variable declarations ? Jerome Glisse
2019-04-17  5:14 ` Julia Lawall
2019-04-17  9:10   ` [Cocci] Add code after local variable declarations? Markus Elfring
2019-04-17  9:12     ` Julia Lawall [this message]
2019-04-17  9:42       ` Markus Elfring
2019-04-17  9:42       ` Markus Elfring
2019-04-17 14:14   ` [Cocci] Add code after local variable declarations ? Jerome Glisse
2019-04-17 14:32     ` Julia Lawall
2019-04-17 16:42     ` [Cocci] Add code after local variable declarations? 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.1904171111410.2612@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).