On Sat, Oct 09, 2010 at 06:40:26PM +0200, Tomas Klacko wrote: > I am including sparse headers in a C++ code, > but this does not work because of the use of keywords > like new and namespace, (and retyping). > > What is your stance on this? > I mean, would you accept a patch or is there > some other way which I have missed? It seems reasonable to avoid the use of C++ keywords in Sparse *headers* (though unnecessary in *source*). Looks like this will primarily cause pain due to "enum namespace" and the various places using it. Seems easy enough to change those all to "ns". "new" mostly seems to get used as a parameter name or local variable name; for the former we could omit it, and for the latter we could trivially call it something more specific like "newlist" or "newptr". So, I'd tend to guess "patches welcome" (again, for headers only, plus minimal corresponding source changes when required). I wouldn't anticipate other Sparse developers objecting strongly, but if they do your mail seems like the right way to find out. The various reasons given for *not* making the Linux kernel headers compatible don't seem to apply here, though. - Josh Triplett -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
