From: julia.lawall@lip6.fr (Julia Lawall) Date: Fri, 18 Nov 2016 21:12:01 +0100 (CET) Subject: [Cocci] Inclusion of script constraints in SmPL In-Reply-To: <24f0d5ad-aae9-70fc-cf66-bd62b001e463@users.sourceforge.net> References: <3c65eb92-8be0-be42-bf8e-893f3853df12@users.sourceforge.net> <32639cf9-b644-0230-02a6-88d66925340e@users.sourceforge.net> <6810eb15-839c-8aa5-6485-401d43ba1246@users.sourceforge.net> <69c3643e-10b4-007a-f847-d0098f298e16@users.sourceforge.net> <5da250c3-e80f-8842-7e85-481cdf6a6259@users.sourceforge.net> <24f0d5ad-aae9-70fc-cf66-bd62b001e463@users.sourceforge.net> Message-ID: To: cocci@systeme.lip6.fr List-Id: cocci@systeme.lip6.fr On Fri, 18 Nov 2016, SF Markus Elfring wrote: > >> Does the script constraint syntax allow more programming language code there? > > > > For all practical purposes, no. > > If you would like to be so strict, I wonder then about the curly brackets > in the published test example. > https://github.com/coccinelle/coccinelle/blob/cbc751b30d9e02390d60ebed643c8e4a3fa0bb2b/tests/idcon_python.cocci#L1 The syntax is curly brackets around a C expression. > > Concretely, the script constraint code is initially parsed using a C parser, > > I find such an information interesting to some degree. > > Why do you pass data to a software component for ?C? at this place? Seemed convenient. Perhaps it could be possible to parse to a closing }, but your goal seems to be to put more complex terms in the script code that might then include }, making things more complicated. > > not a parser for the script language. > > I do not see that would be needed in the restricted use case. > > > > Function calls, of the form f(a,b,c) are in the intersection of C and the > > supported scripting languages. > > Have you got more control about the construction of a single function call? No. julia