Using the iteration functionality, you can start up as many applications
of the semantic patch as you like, parameterized by as many values of
virtual identifiers as you like.
I agree that the evaluation of a filter pattern template is an alternative
design option for the desired source code analysis when each function name will
be passed as a single parameter from an external loop. I assume that this
approach would be less efficient than the other variant where the list of
functions (with a non-void return type) should be checked for their failure
predicates at one place.
Would anybody (besides me) be interested to look at differences in the
corresponding execution speed and the performance characteristics for a wide
selection?
I have got another potentially useful idea for this context.
Is it possible to assign a long regular expression to a SmPL meta-variable which
would be constructed by your supported programming language(s)?
Regards,
Markus
_______________________________________________
Cocci mailing list
[email protected]
http://lists.diku.dk/mailman/listinfo/cocci
(Web access from inside DIKUs LAN only)
