> It doesn't matter, as long as the type is available. I suggest to make the circumstances better known when this will be the case. >> How do you think about reuse another data type enumeration there? > > No idea what you mean by this. A SmPL variable can also be connected with a data type list which is discussed here. >> How would you like to manage names for functions which are not defined >> in the current source file? > > Why does it matter in this case? * Will a command-line parameter like "--include-headers-for-types" be needed here? * Would it make sense to work with function name lists in SmPL constraints? Will any fine-tuning be needed for the execution speed of the evolving source code analysis? Regards, Markus -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html