From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] script code on metavariables
Date: Mon, 18 Jan 2016 11:30:15 +0100 [thread overview]
Message-ID: <569CBEB7.1030509@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1601181112390.2520@hadrien>
>>> The expression should return true or false, ie true if the proposed value
>>> of p is acceptable as a match, and false if it is not.
>>
>> Do you describe the introduction of generic predicate functions here?
>
> I don't understand the question.
I try another wording ?
> In any case, the script doesn't define functions, due to the very limited syntax.
Do you exclude function definitions there so far?
Does the described SmPL extension correspond to predicate functionality?
> The normal case woudl be to define some functions in the initialize rule
> of the semantic patch, and just call them here.
I like such source code organisation in principle for some use cases.
Will this aspect need further considerations because of the evolving
parallelisation support?
https://github.com/coccinelle/coccinelle/issues/50
Regards,
Markus
next prev parent reply other threads:[~2016-01-18 10:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 8:47 [Cocci] script code on metavariables Julia Lawall
2016-01-18 10:11 ` SF Markus Elfring
2016-01-18 10:15 ` Julia Lawall
2016-01-18 10:30 ` SF Markus Elfring [this message]
2016-01-18 10:43 ` Julia Lawall
2016-01-18 12:00 ` SF Markus Elfring
2016-01-18 12:05 ` Julia Lawall
2016-01-18 12:28 ` SF Markus Elfring
2016-01-18 20:25 ` [Cocci] Documentation check for parallelisation support? 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=569CBEB7.1030509@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.