From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Subject: Re: [cocci] Improving support for argument lists with SmPL
Date: Mon, 25 Mar 2024 13:20:44 +0100 [thread overview]
Message-ID: <cf2d5224-3690-4e80-895f-b0a950a5d7ed@web.de> (raw)
In-Reply-To: <52f9f4a8-ba34-f6ec-9bb5-1b96d5fb2674@inria.fr>
>>>> Improve support for handling arguments of function-like macros
>>>> 2024-03-14
>>>> https://github.com/coccinelle/coccinelle/issues/362
…
>> How many programming interfaces can be shared by the Coccinelle software for
>> data processing according to macro calls and handling of attributes with arguments?
>
> Coccinelle makes no distinction between macro calls and function calls.
I got the impression that case distinctions should be enhanced here.
> But if this is again about your question about non-expressions in macro
> arguments, nothing is going to happen. The issue is rare
I suggest to reconsider such a view.
> and is not a priority.
Further improvements would be nice for several issues.
>> See also another related clarification approach (from yesterday):
>> Fix a parse error for the addition of a special variable declaration
>> https://github.com/coccinelle/coccinelle/issues/363#issuecomment-2016794266
>
> I don't see what that has to do with macro arguments.
How would you like to handle argument lists for attributes?
> Please don't mix
> issues in a single message, especially when the message doesn't even make
> clear what the issue is (giving a link dones't count as making it clear).
Do you find a referenced message more interesting for further clarifications?
Markus_Elfring@Sonne:…/Projekte/Coccinelle/janitor> spatch --parse-cocci reduce_scope_for_smart_pointers_in_ice-9-20240324.cocci
…
warning: find: metavariable release not used in the - or context code
…
Regards,
Markus
prev parent reply other threads:[~2024-03-25 12:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 9:01 [cocci] Improving support for argument lists with SmPL Markus Elfring
2024-03-25 10:18 ` Julia Lawall
2024-03-25 11:55 ` Markus Elfring
2024-03-25 12:04 ` Julia Lawall
2024-03-25 12:20 ` Markus Elfring [this message]
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=cf2d5224-3690-4e80-895f-b0a950a5d7ed@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--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 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.