> A bit of information is provided about special “semantics” (also in the manual > for the semantic patch language). The usage of the semantic match functionality influences which default semantics should be applied for the evaluation of an SmPL rule. I imagine that the corresponding data processing can become more interesting when the needed semantics would actually be the opposite setting. * Do you tend to look for the existence of selected implementation details more than that source code variants can occur on all executions paths according to evolving control flows? * Would you expect to use the source code search parameter “exists” more often then “forall”? Regards, Markus
