cocci.inria.fr archive mirror
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Chuhong Yuan <hslester96@gmail.com>, cocci@systeme.lip6.fr
Subject: Re: [Cocci] How to match function calls in macros?
Date: Tue, 19 May 2020 13:23:27 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.2005191321270.2503@hadrien> (raw)
In-Reply-To: <5c451649-4077-e54c-e01d-6bdbc0d02046@web.de>

[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]



On Tue, 19 May 2020, Markus Elfring wrote:

> >> Can the semantic patch language help to insist for a search that a bit
> >> of source code belongs to the implementation of a function-like macro?
> >
> > That's what the search that was written does.  The pattern that comes
> > after #define has to be in the definition of the macro.
>
> I suggest to consider additional source code variants.
> With which SmPL constructs should be ensured that a search pattern
> like “<+... f(...) ...+>” refers only to content from the same logical source line?
> https://en.cppreference.com/w/c/language/translation_phases#Phase_2

Please stop asking the same question over and over.  In the context of a
macro definition, <+... f(...) ...+> will only match what is from the same
logical source line.  Because that is all that there is in a macro
definition.  If Coccinelle is working on a macro definition, it works only
on that macro definition.  If it is working on a function definition, it
works only on that function definition.

julia

[-- Attachment #2: Type: text/plain, Size: 136 bytes --]

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

  reply	other threads:[~2020-05-19 11:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-18  8:26 [Cocci] How to match function calls in macros? Markus Elfring
2020-05-18  9:19 ` 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 [this message]
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=alpine.DEB.2.21.2005191321270.2503@hadrien \
    --to=julia.lawall@inria.fr \
    --cc=Markus.Elfring@web.de \
    --cc=cocci@systeme.lip6.fr \
    --cc=hslester96@gmail.com \
    /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).