From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] Handling of pointer expressions by SmPL
Date: Wed, 19 Jun 2019 13:20:44 +0200 [thread overview]
Message-ID: <0497ec0c-e9a8-a058-355c-4ba90295075d@web.de> (raw)
In-Reply-To: <alpine.DEB.2.20.1906191223350.3726@hadrien>
> You can't specify pointer dereferences by metavariables.
Thanks for another clarification for a detail by the Coccinelle software.
I assumed that this would be useful functionality for the specification
“expression *X;”.
> The pattern is only in the pattern. It is not partly in the metavariables.
Would you like to add this information to the software documentation?
* Does the asterisk express only a specific restriction on the
metavariable type then?
* Which source code would you match (or exclude) for pointer expressions?
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-06-19 11:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-16 20:07 [Cocci] Checking for a null pointer with SmPL Markus Elfring
2019-06-16 20:15 ` Julia Lawall
2019-06-17 5:44 ` Markus Elfring
[not found] ` <alpine.DEB.2.21.1906170747030.2965@hadrien>
2019-06-17 6:04 ` Markus Elfring
2019-06-17 6:07 ` Julia Lawall
2019-06-17 6:14 ` Markus Elfring
[not found] ` <alpine.DEB.2.21.1906170830240.2965@hadrien>
2019-06-17 6:38 ` Markus Elfring
[not found] ` <alpine.DEB.2.20.1906170938530.3699@hadrien>
2019-06-17 16:42 ` Markus Elfring
2019-06-18 6:33 ` Markus Elfring
[not found] ` <alpine.DEB.2.20.1906180936090.3707@hadrien>
2019-06-18 8:10 ` Markus Elfring
2019-06-18 17:27 ` Markus Elfring
[not found] ` <alpine.DEB.2.20.1906181932030.25567@hadrien>
2019-06-18 18:11 ` Markus Elfring
2019-06-19 6:11 ` [Cocci] Handling of pointer expressions by SmPL Markus Elfring
[not found] ` <alpine.DEB.2.21.1906190843070.2687@hadrien>
2019-06-19 7:01 ` Markus Elfring
2019-06-19 8:11 ` Julia Lawall
2019-06-19 8:26 ` Markus Elfring
[not found] ` <alpine.DEB.2.20.1906191223350.3726@hadrien>
2019-06-19 11:20 ` Markus Elfring [this message]
[not found] ` <alpine.DEB.2.20.1906191321480.3726@hadrien>
2019-06-19 11:40 ` Markus Elfring
2019-06-19 11:40 ` 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=0497ec0c-e9a8-a058-355c-4ba90295075d@web.de \
--to=markus.elfring@web.de \
--cc=cocci@systeme.lip6.fr \
--cc=julia.lawall@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.