All of lore.kernel.org
 help / color / mirror / Atom feed
From: julia.lawall@lip6.fr (Julia Lawall)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Easier search for assignment targets with SmPL
Date: Tue, 23 May 2017 11:06:13 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1705231105350.2972@hadrien> (raw)
In-Reply-To: <01dd4e26-0864-df8e-4b43-e054c0e61400@users.sourceforge.net>



On Tue, 23 May 2017, SF Markus Elfring wrote:

> >  var = action(...);
>
> This specification looks also simple for the semantic patch language
> at first glance.
> I tried to express that a specific value is assigned to something.
> But this ?something? could be a different item depending on the position
> in the source code.
>
> 1. Variable
> 2. Expression
> 3. Element for a designated initialiser
>
> I would appreciate if I do not need to repeat specifications for these cases
> in SmPL code. How do you think about the possibility to support the desired
> source code search by an additional metavariable type there?
> Can it become safer and more convenient to handle assignments here?

I have no idea what you are asking for.  In any case, an expression
metavariable already matches a variable.  I don't know what a designated
initializer is.

julia

>
> Regards,
> Markus
> _______________________________________________
> Cocci mailing list
> Cocci at systeme.lip6.fr
> https://systeme.lip6.fr/mailman/listinfo/cocci
>

  reply	other threads:[~2017-05-23  9:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-14 15:41 [Cocci] Checking exception handling implementations with SmPL SF Markus Elfring
2017-05-18 13:00 ` [Cocci] Checking source code (including optional parts) " SF Markus Elfring
2017-05-18 15:21 ` [Cocci] Safe determination of function properties for SmPL scripts SF Markus Elfring
2017-05-18 16:00 ` [Cocci] Checking failure predicates with SmPL SF Markus Elfring
2017-05-23  9:01 ` [Cocci] Easier search for assignment targets " SF Markus Elfring
2017-05-23  9:06   ` Julia Lawall [this message]
2017-05-23 10:52     ` SF 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.20.1705231105350.2972@hadrien \
    --to=julia.lawall@lip6.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.