From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Avoiding code duplication for SmPL constraints
Date: Sat, 17 Feb 2018 14:34:49 +0100 [thread overview]
Message-ID: <06b4669e-7419-e4f8-1761-4e58eef44fbd@users.sourceforge.net> (raw)
Hello,
Constraints can be specified for metavariables of the semantic patch language.
I noticed that they can trigger software maintenance challenges
when bigger specifications are repeated in some SmPL rules.
Now I am looking again for further possibilities to avoid corresponding
code duplication.
* Scripted constraints might be a design option.
Unfortunately, I find the documentation for this functionality still incomplete.
* I imagine that it would nice if constraints could be set by programming script
rules at a single place.
Regards,
Markus
next reply other threads:[~2018-02-17 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-17 13:34 SF Markus Elfring [this message]
2018-02-17 13:39 ` [Cocci] Avoiding code duplication for SmPL constraints Julia Lawall
[not found] ` <388d5af8-d3e4-ee18-7481-3675e2b52024@users.sourceforge.net>
2018-02-17 14:11 ` Julia Lawall
[not found] ` <9d550db4-cad4-f625-32da-173078fdde54@users.sourceforge.net>
2018-02-17 14:34 ` [Cocci] Clarification for scripted " Julia Lawall
2018-02-17 14:54 ` SF 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=06b4669e-7419-e4f8-1761-4e58eef44fbd@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--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 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.