>> But I have got difficulties to interpret it in an useful way. > > Coccinelle follows control-flow paths.
This information is generally fine. > Thers is a control-flow path from the bottom of a loop back up to the top. I can not follow with my intermediate understanding to such a view at the moment. Why was the combination of a call for the function “strncmp” before a “queuefree” really displayed as an update candidate? >>> @usage@ >>> identifier action, member, release=~"^.+free$"; >>> expression context,e; >>> @@ >>> *release(context); >>> ... when != context = e >>> when any // to get all results >>> *action(..., (context)->member, ...) >> >> Should the SmPL construct “<+.. ...+>” work also similar to your suggestion? > > <+... ...+> would also not allow context = e after the last match of the > pattern inside the nest. This information sounds promising. I am looking still for possibilities to clarify the overlap better in the shown functionality. > A when on a <+... ...+> applies to the entire matched region. Can the parameter “when” be combined with this construct anyhow? Regards, Markus _______________________________________________ Cocci mailing list [email protected] https://systeme.lip6.fr/mailman/listinfo/cocci
