Closed elfring closed 9 years ago
As per my comments from seL4/camkes#1 and others.
This issue was resolved in 2b860d1de1ca4dc896c3fa836fd5a91df20794b4. Can someone please close?
Would you also like to reconsider the use of the remaining double underscores in affected identifiers according to the naming convention of the C++ language standard?
There is no C++ code in this repository, so I don't think that makes sense.
Would you like to support for your software that the corresponding source files can also be safely handled by C++ compilers?
We do not. This software does not run in an environment that supports C++ and should not be used with a C++ compiler.
I would like to point out that identifiers like "
__CAPDL_H__
" and "__CAPDL_SPEC_H__
" do not fit to the expected naming convention of the C language standard. Would you like to adjust your selection for unique names?