With your strategy, it would not be possible to write rules that match on uses of macros. This can be quite useful, especially in the case of named constants, eg #define DONE 0.
I guess that a further clarification of the involved details would be interesting.
It doesn't know what is needed. You can control the degree of effort it puts into finding the files, but that is quite coarse-grained.
I assume that the tool should know the needed source code parts because of the (un)defined preprocessor symbols. Can it be that a few too many header files get included which result in the error messages about missing files?
If you want feedback about the degree to which you code can be parsed, you can use the -parse_c option, perhaps additionally with -verbose_parsing, if you want more information.
Thanks for this hint. - I'm curious when the tool will process also function prototypes from header files like "stdio.h" and "signal.h" for my test case.
Regards, Markus _______________________________________________ Cocci mailing list [email protected] http://lists.diku.dk/mailman/listinfo/cocci (Web access from inside DIKUs LAN only)
