> The idea with the script constraints on metavariables feature is that the
> script code there should only contain a function call.

I would like to add another view to this software evolution for
further considerations.
The purpose of such a function call can be interpreted in different ways,
can't it?

1. I get the impression from the word “constraint” that something should
   be restricted. Does this aspect mean that the functionality is finally
   mapped to a predicate?

2. Can it be also used as a data generator or content provider for any other
   non-boolean value?

Regards,
Markus
_______________________________________________
Cocci mailing list
[email protected]
https://systeme.lip6.fr/mailman/listinfo/cocci

Reply via email to