Closed elfring closed 3 months ago
@elfring Have you observed any name clash with reserved names ?
:thought_balloon: How do you think about to avoid that this software depends on undefined behaviour?
According to C standard, rule 7.1.3 states
Do not declare or define a reserved identifier All identifiers that begin with an underscore and either an uppercase letter or another underscore are always reserved for any use. All identifiers that begin with an underscore are always reserved for use as identifiers with file scope in both the ordinary and tag name spaces. Each macro name in any of the following subclauses (including the future library directions) is reserved for use as specified if any of its associated headers is included, unless explicitly stated otherwise. All identifiers with external linkage (including future library directions) and errno are always reserved for use as identifiers with external linkage. Each identifier with file scope listed in any of the following subclauses (including the future library directions) is reserved for use as a macro name and as an identifier with file scope in the same name space if any of its associated headers is included.
I would appreciate if CMSIS DSP headers could be made compliant to this rule.
:crystal_ball: Do name conventions for C++ code matter for your software?
I would like to point out that identifiers like “
_MATRIX_UTILS_H_
” and “_TRANSFORM_FUNCTIONS_H_
” do not fit to the expected naming convention of the C++ language standard. Would you like to adjust your selection for unique names?