From: elfring@users.sourceforge.net (SF Markus Elfring) Date: Fri, 18 Nov 2016 19:00:04 +0100 Subject: [Cocci] Inclusion of script constraints in SmPL In-Reply-To: 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> Message-ID: <5da250c3-e80f-8842-7e85-481cdf6a6259@users.sourceforge.net> To: cocci@systeme.lip6.fr List-Id: cocci@systeme.lip6.fr >> * Would such an inclusion approach trigger special requirements on the >> position for corresponding initialisation code? > > The constraint specification should be a single function call. Does the script constraint syntax allow more programming language code there? > You can set up your @initialize:python@ code to import whatever you want. I would prefer to keep initialisation code for the implementation of the predicate function closely together with the call of the included metavariable. Regards, Markus