From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Cc: kernel-janitors@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Improved handling of member access operators with SmPL expression variables
Date: Sun, 30 Aug 2026 10:45:59 +0200 [thread overview]
Message-ID: <30b81b65-77cf-4a3f-b384-e622954564a3@web.de> (raw)
In-Reply-To: <a7ce1c69-a6d9-e535-2bff-d16627ecfdee@inria.fr>
>> Another SmPL script example:
>> @my_test@
>> expression hint;
>> @@
>> *hint->hint
>>
>>
>> Questionable test result (also according to the software combination “Coccinelle 1.3.2”):
>> Markus_Elfring@Sonne:…/Projekte/Coccinelle/Probe> spatch --parse-cocci show_expression_for_same_member_name.cocci
>> …
>> minus: parse error:
>> File "show_expression_for_same_member_name.cocci", line 4, column 7, charpos = 37
>> around = 'hint',
>> whole content = *hint->hint
>>
>>
>> How will development interests evolve to improve affected software components?
>> https://en.cppreference.com/c/language/operator_member_access#Member_access
>
> They will not improve. Proposed changes will be NACKed. Please stop
> asking for this. It is not in the spirit of the language.
I hope that I can convince contributors for further development possibilities.
Regards,
Markus
next prev parent reply other threads:[~2026-08-30 8:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-30 8:15 [RFC] Improved handling of member access operators with SmPL expression variables Markus Elfring
[not found] ` <a7ce1c69-a6d9-e535-2bff-d16627ecfdee@inria.fr>
2026-08-30 8:45 ` Markus Elfring [this message]
2026-08-30 10:10 ` 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=30b81b65-77cf-4a3f-b384-e622954564a3@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=julia.lawall@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.