Make sure that included header file names are unique. According to the C standard [ISO/IEC 9899:2011],
The implementation shall provide unique mappings for sequences consisting of one or more nondigits or digits (188.8.131.52) followed by a period (.) and a single nondigit. The first character shall not be a digit. The implementation may ignore distinctions of alphabetical case and restrict the mapping to eight significant characters before the period.
This means that
- Only the first eight characters in the file name are guaranteed to be significant.
- The file has only one nondigit character after the period in the file name.
- The case of the characters in the file name is not guaranteed to be significant.
To guarantee that header file names are unique, all included files should differ (in a case-insensitive manner) in their first eight characters or in their (one-character) file extension.
Note that compliance with this recommendation does not require that short file names are used, only that the file names are unique.
Noncompliant Code Example
The following noncompliant code contains references to headers that may exist independently in various environments but can be ambiguously interpreted by a C-compliant compiler.
library.h may refer to the same file. Also, because only the first eight characters are guaranteed to be significant, it is unclear whether
utilities_physics.h are parsed. Finally, if a file such as
my_libraryOLD.h exists, it may inadvertently be included instead of
This compliant solution avoids the ambiguity by renaming the associated files to be unique under the preceding constraints.
The only solution for mitigating ambiguity of a file, such as
my_libraryOLD.h, is to rename old files with either a prefix (that would fall within the first eight characters) or add an extension (such as
PRE08-EX1: While the C standard requires only the first eight characters in the file name to be significant, most modern systems have long file names, and compilers on such systems can typically differentiate them. Consequently, long file names in headers may be used, provided that all the implementations to which the code is ported can distinguish between these file names.
Failing to guarantee uniqueness of header files may result in the inclusion of an older version of a header file, which may include incorrect macro definitions or obsolete function prototypes or result in other errors that may or may not be detected by the compiler. Portability issues may also stem from the use of header names that are not guaranteed to be unique.
Search for vulnerabilities resulting from the violation of this rule on the CERT website.
ISO/IEC 9899:2011 Section 6.10.2, "Source file inclusion"
MISRA Rule 19.5