From: Markus Elfring <Markus.Elfring@web.de>
To: Coccinelle <cocci@systeme.lip6.fr>
Subject: [Cocci] Object-orientation for metavariables
Date: Sun, 2 Jun 2019 14:44:37 +0200 [thread overview]
Message-ID: <5591f13c-07b6-0123-1637-8d6d6460f4da@web.de> (raw)
Hello,
The metavariables of the semantic patch variables provide a programming
interface for various information from source code.
They were designed in the way so far that a single primary content is handled.
The contents can refer also to more detailed data structures then.
The system default is to return all structure members together.
I imagine that advanced source code analysis will trigger the need to work
only with parts on concrete demand.
Thus I propose to delegate the selection of desired data sources to
corresponding functions (or methods).
How do you think about software extensions in such a direction?
https://github.com/coccinelle/coccinelle/issues/22
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
reply other threads:[~2019-06-02 12:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5591f13c-07b6-0123-1637-8d6d6460f4da@web.de \
--to=markus.elfring@web.de \
--cc=cocci@systeme.lip6.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 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).