Page History

...

<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="94173e972db3d574-02199203-481d45d0-b762863c-61415704953c688749e44d7a"><ac:parameter ac:name="">1</ac:parameter></ac:structured-macro> \[1\] Note that the POSIX ^&#xAE;^ standard extends the set of identifiers reserved by C99 to include an open-ended set of its own. See section [2.2 Compilation Environment|http://www.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html#tag_15_02] in [IEEE Std 1003.1-2008|AA. References#IEEE Std 1003.1-2008].

...

A common but noncompliant practice is to choose a reserved name for a macro used in a preprocessor conditional guarding against multiple inclusion of a header file. See also guideline recommendation PRE06-C. Enclose header files in an inclusion guard. The name may clash with reserved names defined by the implementation of the C standard library in its headers, or with reserved names implicitly predefined by the compiler, even when no C standard library header is included. A typical manifestation of such a clash is a compilation error.

...

Related Guidelines

CERT C++ Secure Coding Standard: DCL32-CPP. Do not use names reserved for the implementation

Bibliography

unmigrated-wiki-markup

\[[ISO/IEC 9899:1999|AA. Bibliography#ISO/IEC 9899-1999]\] Section 7.1.3, "Reserved Identifiers"

Bibliography

[\[IEEE Std 1003.1-2008\]|AA. References#IEEE Std 1003.1-2008] Section 2.2 "The Compilation Environment"

...

      02. Declarations and Initialization (DCL)      DCL38-C. Use the correct syntax when declaring flexible array members