Hello,
I became curious if further developers would like to try the following script out
for the semantic patch language.
@display@
identifier action;
type t;
@@
*t * action(...)
{
... when any
}
I interpret such a search approach in the way that it should extract some data
from a lot of source code places.
Thus I imagine that it results also in special software run time characteristics
which matter especially for big codebases like Linux.
How do you think about to clarify corresponding data collections
and computation resources?
Related source code analysis concerns can eventually be also clarified.
* Handling of function declarations in header files
* Relevance of some preprocessor directives
Regards,
Markus
