From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Chuhong Yuan <hslester96@gmail.com>, cocci@systeme.lip6.fr
Subject: Re: [Cocci] How to match function calls in macros?
Date: Mon, 18 May 2020 10:26:52 +0200 [thread overview]
Message-ID: <4a677190-b494-138c-4782-eec033a77377@web.de> (raw)
> @@
> identifier mac,f;
> @@
>
> *#define mac(...) <+... f(...) ...+>
Does such an analysis approach restrict the source code search really on
complete definitions for function-like macros?
Will it become interesting for clarify corresponding special cases?
* How are empty macros treated by the Coccinelle software?
* Is there a connection managed between a macro declaration
and subsequent source code?
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next reply other threads:[~2020-05-18 8:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 8:26 Markus Elfring [this message]
2020-05-18 9:19 ` [Cocci] How to match function calls in macros? Julia Lawall
2020-05-18 10:13 ` Markus Elfring
2020-05-18 10:18 ` Julia Lawall
2020-05-18 10:30 ` Markus Elfring
2020-05-18 10:34 ` Julia Lawall
2020-05-18 10:46 ` Markus Elfring
2020-05-18 10:50 ` Julia Lawall
2020-05-18 11:07 ` Markus Elfring
2020-05-19 11:15 ` Markus Elfring
2020-05-19 11:23 ` Julia Lawall
2020-05-19 11:43 ` Markus Elfring
2020-05-19 11:55 ` Julia Lawall
2020-05-19 12:04 ` Markus Elfring
2020-05-18 12:07 ` Markus Elfring
-- strict thread matches above, loose matches on Subject: below --
2020-05-16 11:42 Markus Elfring
2020-05-16 8:16 Chuhong Yuan
2020-05-16 8:49 ` Julia Lawall
2020-05-16 12:26 ` Chuhong Yuan
2020-05-16 12:45 ` Julia Lawall
2020-05-16 14:17 ` Chuhong Yuan
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=4a677190-b494-138c-4782-eec033a77377@web.de \
--to=markus.elfring@web.de \
--cc=cocci@systeme.lip6.fr \
--cc=hslester96@gmail.com \
--cc=julia.lawall@inria.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).