From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr, kernel-janitors@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [RFC] Improved handling of member access operators with SmPL expression variables
Date: Sun, 30 Aug 2026 10:15:17 +0200 [thread overview]
Message-ID: <fc7bba15-5116-4467-bce1-be8ff3859184@web.de> (raw)
Hello,
I pointed out that some data processing can be achieved by the means of
the semantic patch language.
SmPL script example:
@display2@
identifier an_item, a_field;
@@
(
*an_item.a_field
|
*an_item->a_field
)
Extend support for data processing with member identifications
2020-09-28
https://github.com/coccinelle/coccinelle/issues/226#issuecomment-699787269
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
Regards,
Markus
next reply other threads:[~2026-08-30 8:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-30 8:15 Markus Elfring [this message]
[not found] ` <a7ce1c69-a6d9-e535-2bff-d16627ecfdee@inria.fr>
2026-08-30 8:45 ` [RFC] Improved handling of member access operators with SmPL expression variables Markus Elfring
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=fc7bba15-5116-4467-bce1-be8ff3859184@web.de \
--to=markus.elfring@web.de \
--cc=cocci@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.