Coccinelle Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Checking data structure modification with SmPL
Date: Sat, 22 Aug 2015 18:50:33 +0200	[thread overview]
Message-ID: <55D8A859.6080409@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1508220903470.2384@hadrien>

>> * Do I need to fiddle with another SmPL disjunction to express
>>   the possibility that "var" could be more than a simple identifier?
> 
> Ultimately, var shouldend up at an identifier, so I don't see the need.

How do you think about a variant like the following?

(expression)->element


>> * How should the support for longer arrow chains be specified?
> 
> No idea what you are asking, but I am not keen on adding yet another
> metavariable type for this, which anyway doesn't correspond to anything in
> the C grammar.

Does the following approach make my consideration a bit more clear?

var->(expression)->(expression)->element


How should a more detailed pointer access variation be handled here?

Regards,
Markus

  reply	other threads:[~2015-08-22 16:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18 11:34 [Cocci] Checking data structure modification with SmPL SF Markus Elfring
2015-08-22 14:17 ` Julia Lawall
2015-08-22 15:58   ` SF Markus Elfring
2015-08-22 16:05     ` Julia Lawall
2015-08-22 16:50       ` SF Markus Elfring [this message]
2015-08-22 19:07         ` Julia Lawall
2015-08-22 20:01           ` SF Markus Elfring
     [not found]             ` <alpine.DEB.2.10.1508221303590.2446@hadrien>
2015-08-22 20:50               ` 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=55D8A859.6080409@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --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