> I've thought such a thing would be useful for C style as well. Right. It just becomes more of an issue if people start using C++ which is a much more complex and large language, but it would also benefit gcc developers today to have C coding standard checked automatically.
> One slight complication is that while a limited subset of C++ should be > fine for most of the compiler, there may be a use for many more features > (provided those features are still supported by the baseline bootstrap > compiler version, e.g. 3.4) in selected areas that provide infrastructure > for use in the rest of the compiler (just as now we have complicated > macros in vec.h, and maintainers need not care most of the time about the > implementations of them, just about how to use them). So you may have > features that should not be freely spread throughout the compiler but > should be allowed for particular pieces of code only. You can use special pragmas or attributes to tell the coding checker which subset is allowed for a given file. Arno
