The function name library sounds like what is implemented in iteration.cocci.

No. - My idea goes into a different direction.

A couple of application programming interfaces are documented. This documentation should clearly indicate which predicate denotes a failed function call.

I imagine that a table can be created with the following columns to store some of the needed knowledge.
- API identifier
- API version
- header file name
- function name
- predicate for failure check

This knowledge should be transformed into a couple of filter patterns to insert advices (emergency brake?) into affected function implementations.


It collects the function that return ERR_PTR, and then
one can do what one wants with that information.

I am more interested to replace the following instructions by a direct source code adjustment.
cocci.print_main("def",p1)
cocci.print_secs("ref",p2)

Regards,
Markus
_______________________________________________
Cocci mailing list
[email protected]
http://lists.diku.dk/mailman/listinfo/cocci
(Web access from inside DIKUs LAN only)

Reply via email to