All of 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 22:50:20 +0200	[thread overview]
Message-ID: <55D8E08C.7010204@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1508221303590.2446@hadrien>

>> * Can each part between the pointer access operators be an expression?
> 
> No.  In a->b->c->d->e, b->c->d has no value.  It even has no meaning
> independent of the type of a.

Which wording would be more appropriate from the point of view
in the syntax of the C programming language?


>> * How long can such a structure member access chain become
>>   in interesting source codes?
> 
> I guess as long as the greatest nesting depth of structures in the program.
> If the program contains structures of recursive type, it ca have
> any length.

Can I prepare SmPL scripts to handle variations there?

How are the chances to avoid the consideration and source code analysis around
only a limited number of structure member accesses?

Regards,
Markus

      parent reply	other threads:[~2015-08-22 20: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
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 [this message]

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=55D8E08C.7010204@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 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.