We try to develop an approach which will be generic enough to analyse a wide
range of source code from various source files. I would prefer to reduce the
number of "left-overs" that remain for harder manual inspection.
I don't think that Coccinelle is designed for this approach.
You know a few design limitations for your software tools. I guess that you
expect that the semantic patch language is powerful already.
If you want to make a tool that does something in a perfect manner on all code
bases,
then you should use some other tool such as CIL or Clang that gives you and API
for accessing the abstract syntax tree and lets you implement whatever analyses
you want.
I hope that further extensions can be considered to come closer to the desired
"perfection". ;-)
http://lists.diku.dk/pipermail/cocci/2011-December/002401.html
Coccinelle is designed for quickly prototyping rules that are typically specific
to a particular code base.
Some efforts are still needed to make a chosen filter pattern complete enough so
that it can be safely applied in a couple of source code situations.
Regards,
Markus
_______________________________________________
Cocci mailing list
[email protected]
http://lists.diku.dk/mailman/listinfo/cocci
(Web access from inside DIKUs LAN only)
