All of lore.kernel.org
 help / color / mirror / Atom feed
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:26:17 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1801061822290.2579@hadrien> (raw)
In-Reply-To: <5fb3bd3a-d78d-7d2c-050f-146887838d95@users.sourceforge.net>



On Sat, 6 Jan 2018, SF Markus Elfring wrote:

> > The simplest thing would be to just print the rule you want in a
> > python/ocaml script rule.
>
> I would like to adjust a SmPL execution environment for special use cases somehow.
> How would ?printing? be useful here?

Well, I was thinking that you could eg make a script like:

@script:ocaml@
e << r.e;
@@

Printf.printf "@@\n";
Printf.printf "expression f;\n";
Printf.printf "@@\n\n";
Printf.printf "-f(%s);\n" e

But I'm not sure that the parser of script code would be happy with a @ in
the script code, so you would have to do some trick to get around that.

>
>
> > Some support was added at one point for generating rules based on matches
> > from other rules,
>
> Such information sounds promising.
>
>
> > but that code has not been maintained, and I don't think it is likely
> > to be updated in the future.
>
> I am curious if there are still any chances to revive corresponding
> approaches.

I'm not interested in spending time on it in the foreseeable future.  If
anyone else wants to, the code is there...  Maybe you put something like
generated in the header of the semantic patch rule, like you might put
script:ocaml.

julia

>
>
> Is it safer therefore to generate advanced SmPL script files by external
> software tools (at the moment)?
>
> Regards,
> Markus
>

  reply	other threads:[~2018-01-06 17:26 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
2018-01-06 17:18   ` SF Markus Elfring
2018-01-06 17:26     ` Julia Lawall [this message]
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.1801061822290.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.