From: julia.lawall@lip6.fr (Julia Lawall)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Automatic generation of SmPL rules by a script rule
Date: Sat, 6 Jan 2018 18:01:59 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1801061800370.2579@hadrien> (raw)
In-Reply-To: <c1e3f44c-63ca-3306-840b-77d677e7e91f@users.sourceforge.net>
On Sat, 6 Jan 2018, SF Markus Elfring wrote:
> Hello,
>
> Is it possible to generate additional rules for a specific execution environment
> of the semantic patch language by an advanced script rule?
>
> Can a special rule generation be avoided from external software tools?
The simplest thing would be to just print the rule you want in a
python/ocaml script rule. Some support was added at one point for
generating rules based on matches from other rules, but that code has not
been maintained, and I don't think it is likely to be updated in the
future.
julia
next prev parent reply other threads:[~2018-01-06 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-06 16:57 [Cocci] Automatic generation of SmPL rules by a script rule SF Markus Elfring
2018-01-06 17:01 ` Julia Lawall [this message]
2018-01-06 17:18 ` SF Markus Elfring
2018-01-06 17:26 ` Julia Lawall
2018-01-06 17:45 ` SF Markus Elfring
2018-01-06 17:59 ` 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.20.1801061800370.2579@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 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.