From: Julia Lawall <julia.lawall@inria.fr>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Luca Coelho <luca@coelho.fi>, cocci@inria.fr
Subject: Re: [cocci] Searching for special function implementations with SmPL
Date: Sat, 28 Jan 2023 10:49:16 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2301281048270.2822@hadrien> (raw)
In-Reply-To: <808cd549-f96d-872d-a4db-30ea33095207@web.de>
[-- Attachment #1: Type: text/plain, Size: 679 bytes --]
On Sat, 28 Jan 2023, Markus Elfring wrote:
> > @@
> > identifier nested_macros.nm;
> > function f;
> > identifier dev_priv;
>
>
> How do you think about to use the following SmPL code variant instead of
> the metavariable type “function”?
>
>
> identifier dev_priv, f;
Good suggestion, Function is not really supported. I think it behaves
just like identifier, but it would be better to just use identifier.
Function was an idea thta never actually got implemented.
julia
>
>
>
> > expression e;
> > @@
> > f(...) {
> > ...
> > - struct drm_i915_private *dev_priv = e;
> > + struct drm_i915_private *i915 = e;
> >
> > <+...nm(...)...+>
> > }
>
> Regards,
> Markus
>
next prev parent reply other threads:[~2023-01-28 9:49 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 17:07 [cocci] Nested macros Luca Coelho
2023-01-27 18:34 ` [cocci] Checking selected macro calls with SmPL Markus Elfring
2023-01-27 20:52 ` [cocci] Nested macros Julia Lawall
2023-01-27 22:00 ` Luca Coelho
2023-01-28 9:19 ` Julia Lawall
2023-01-28 9:25 ` Luca Coelho
2023-01-28 9:46 ` [cocci] Searching for special function implementations with SmPL Markus Elfring
2023-01-28 9:49 ` Julia Lawall [this message]
2023-01-28 10:03 ` Luca Coelho
2023-01-28 13:33 ` Julia Lawall
2023-01-29 16:39 ` Luca Coelho
2023-01-29 17:28 ` Julia Lawall
2023-01-29 17:55 ` Luca Coelho
2023-01-29 19:15 ` Luca Coelho
2023-01-29 20:09 ` Julia Lawall
2023-01-30 6:32 ` Luca Coelho
2023-01-30 8:37 ` Julia Lawall
2023-01-30 8:50 ` Luca Coelho
2023-01-30 8:56 ` Julia Lawall
2023-01-30 9:05 ` Luca Coelho
2023-01-30 9:34 ` Markus Elfring
2023-01-30 9:41 ` Luca Coelho
2023-01-30 9:50 ` Markus Elfring
2023-01-30 9:52 ` Luca Coelho
2023-01-30 9:55 ` Julia Lawall
2023-01-30 10:07 ` Markus Elfring
2023-01-30 10:47 ` Julia Lawall
2023-01-30 10:59 ` Luca Coelho
2023-01-30 11:25 ` Markus Elfring
2023-01-31 15:57 ` Luca Coelho
2023-01-31 15:59 ` Luca Coelho
2023-01-31 16:08 ` Julia Lawall
2023-01-31 16:10 ` Luca Coelho
2023-01-31 16:20 ` Julia Lawall
2023-01-29 18:01 ` [cocci] Adding a parameter for special macro calls " Markus Elfring
2023-01-29 19:11 ` Luca Coelho
2023-01-28 13:43 ` [cocci] Searching for special function implementations " Markus Elfring
2023-01-29 16:41 ` Luca Coelho
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.22.394.2301281048270.2822@hadrien \
--to=julia.lawall@inria.fr \
--cc=Markus.Elfring@web.de \
--cc=cocci@inria.fr \
--cc=luca@coelho.fi \
/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.