All of lore.kernel.org
 help / color / mirror / Atom feed
From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Automatic generation of SmPL rules by a script rule
Date: Sat, 6 Jan 2018 18:45:05 +0100	[thread overview]
Message-ID: <e6fec4c0-eec1-d6cd-4928-7ad785be7ba4@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1801061822290.2579@hadrien>

> 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

I would prefer to use the available programming languages directly
instead of starting the spatch program for such file generation.


> 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.

Would you like to continue the clarification for the topic ?Configuration
or escaping of @ characters for embedded programming language scripts??
https://github.com/coccinelle/coccinelle/issues/36


> I'm not interested in spending time on it in the foreseeable future.

But I imagine that I would like to show related update suggestions
around SmPL scripts because of other approaches then.
Will alternatives become useful?


> If anyone else wants to, the code is there...

Would you like to point any specific source files out for the current
intermediate development status?

Regards,
Markus

  reply	other threads:[~2018-01-06 17:45 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
2018-01-06 17:45       ` SF Markus Elfring [this message]
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=e6fec4c0-eec1-d6cd-4928-7ad785be7ba4@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.