From: julia.lawall@lip6.fr (Julia Lawall)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Dummy rule for simplifying "depends on" clauses?
Date: Wed, 10 Oct 2018 10:11:07 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1810101010060.2477@hadrien> (raw)
In-Reply-To: <9e5331dd-ca41-845b-3852-29941fde1652@users.sourceforge.net>
On Wed, 10 Oct 2018, SF Markus Elfring wrote:
> > @dummy depends on rule1 || rule2 || rule3@
> >
> > I guess that the problem is that you have to give dummy a pattern
> > that will always match.
>
> Can a software extension make sense for the semantic patch language
> so that the specification of an always matching source code search
> pattern can be omitted?
>
> How do you think about an additional key word in the SmPL rule header?
I think that there are enough keywords already. Perhaps allowing no
pattern could be permitted, but the problem seems rare.
julia
next prev parent reply other threads:[~2018-10-10 8:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 22:30 [Cocci] Dummy rule for simplifying "depends on" clauses? Timur Tabi
2018-10-10 5:43 ` Julia Lawall
[not found] ` <9e5331dd-ca41-845b-3852-29941fde1652@users.sourceforge.net>
2018-10-10 8:11 ` Julia Lawall [this message]
2018-10-10 15:33 ` Timur Tabi
2018-10-10 15:32 ` Timur Tabi
2018-10-10 15:36 ` Julia Lawall
2018-10-10 16:02 ` Timur Tabi
2018-10-10 16:10 ` Julia Lawall
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=alpine.DEB.2.21.1810101010060.2477@hadrien \
--to=julia.lawall@lip6.fr \
--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).