On Sat, 26 Sep 2015, SF Markus Elfring wrote: > > 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. It is like for the type of anything. If the declaration of the thing is available with the type information, eg in the same file or an included header file, then the type will be available. If the declaration is not available then the type will not be available. > >> 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. One type, more that one type, it doesn't matter. > >> 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? This argument is never needed. It is only an optimization. It means that he header files are only considered when collecting type information, but not whn doing transformation. But this argument has no effect on the set of types tha are available. julia > * 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
