Closed elfring closed 10 years ago
But APULSE__TRACE_H
doesn't have any leading or trailing underscores. Eh?
How do you think about to read corresponding information sources that describe the consequences of underscores in such identifiers?
Thanks for the links, they look interesting.
How do you think about to avoid that this software depends on undefined behaviour? Would you like to rename affected include guards?
As far as I understand, two consecutive underscored are reserved in C++ only. Since this project uses C solely, that's OK.
Would you like to support that your software can also be correctly processed by C++ compilers?
Nope.
I would like to point out that identifiers like "
APULSE__TRACE_H
" and "APULSE__UTIL_H
" do not fit to the expected naming convention of the C++ language standard. Would you like to adjust your selection for unique names?