> It uses a regular expression to detect that a statement starts with the > word ASSERT, and matches the next statement as well, and then in another > rule adds a ; before the subsequent statement.
Can related improvements for the supported programming interfaces help to split the available information into more useful pieces? > If you add the ; after the ASSERT statement it comes out after ASSERT, > not after the commented argument list. But with this semantic patch, > the ; comes out on a line of its own, and would have to be moved up manually. Can this software behaviour be avoided if the semicolon would be inserted by using the function “make_stmt” of Coccinelle's library in a SmPL script rule? Regards, Markus _______________________________________________ Cocci mailing list [email protected] https://systeme.lip6.fr/mailman/listinfo/cocci
