cocci.inria.fr archive mirror
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Coccinelle <cocci@systeme.lip6.fr>
Subject: [Cocci] Challenges around asterisk usage in SmPL code
Date: Sat, 24 Aug 2019 19:33:29 +0200	[thread overview]
Message-ID: <a7f12c28-0f96-d388-f1f4-57db4d3d880d@web.de> (raw)

Hello,

The programming languages “C” and “C++” support functionality where characters
can be ambiguous:
The asterisk can be used for the specification of multiplications
or pointer dereferences (for example).
https://softwareengineering.stackexchange.com/questions/124570/why-pointer-symbol-and-multiplication-sign-are-same-in-c-c

Now I would like to specify a source code search for the case that
unary operations would be used within computations.
The Coccinelle software accepts the following approach.

@assignment@
expression x, y;
@@
* y = ... *(x) ...;


I became curious if another small script for the semantic patch languages
should also work then.

@check@
expression x, y;
statement es;
@@
*if ( \( !(x) \| x == NULL \) )
*   y = ... *(x) ...;
 else
    es


But a parse error is reported so far for this code variant.
How will the software situation evolve further around such challenges?

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

             reply	other threads:[~2019-08-24 17:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-24 17:33 Markus Elfring [this message]
     [not found] ` <2AE15A09-F219-43DC-81A9-73C13CFC0753@lip6.fr>
2019-08-25  7:40   ` [Cocci] Challenges around asterisk usage in SmPL code Markus Elfring
2019-08-25  7:48     ` Julia Lawall
2019-08-25  8:13       ` Markus Elfring
2019-08-25  8:30       ` [Cocci] Searching for unary operations with SmPL Markus Elfring
2019-08-25  9:11       ` [Cocci] Challenges around asterisk usage in SmPL code Markus Elfring
2019-08-25  9:45         ` Julia Lawall
2019-08-25 10:22           ` Markus Elfring
2019-08-25 13:13             ` [Cocci] Checking information from “--parse-cocci” Markus Elfring
     [not found]               ` <alpine.DEB.2.21.1908252118210.2801@hadrien>
2019-08-25 13:45                 ` Markus Elfring
     [not found]                   ` <alpine.DEB.2.21.1908252209170.3506@hadrien>
2019-08-25 14:19                     ` Markus Elfring
2019-08-25 17:34           ` [Cocci] Challenges around asterisk usage in SmPL code Markus Elfring
2019-08-26 17:26           ` [Cocci] Checking null pointer handling with SmPL Markus Elfring
2019-08-27  0:58             ` Julia Lawall
2019-08-28 11:50               ` 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=a7f12c28-0f96-d388-f1f4-57db4d3d880d@web.de \
    --to=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).