If a file with the same name as a standard header is placed in the search path for included source files, the behavior is undefined.
The following table from the C Standard, subclause 7.1.2 [ISO/IEC 9899:2011], lists these standard headers:
<complex<ctype<errno<fenv<float<iso646<limits<locale<math<setjmp<stdarg<stdbool<stddef<stdint<stdio<stdlib<string<stdint.h> | <tgmath.h> | <wctype.h> |
<time<wchar<wctype<uchar Do not reuse standard header file names, system-specific header file names, or other header file names.
...
In this noncompliant code example, the programmer chooses to use a local version of the standard library but does not make the change clear.:
| Code Block |
|---|
| bgColor | #FFcccc |
|---|
| lang | c#ffcccc |
|---|
|
#include "stdio.h" /* confusingConfusing, distinct from <stdio.h> */
/* ... */
|
...
The solution addresses the problem by giving the local library a unique name (as per PRE08-C. Guarantee that header file names are unique), which makes it apparent that the library used is not the original.:
| Code Block |
|---|
| bgColor | #ccccFF |
|---|
| lang | c#ccccff |
|---|
|
/* Using a local version of stdio.h */
#include "mystdio.h"
/* ... */
|
...
Using header file names that conflict with other header file names can result in an incorrect file being included.
Recommendation | Severity | Likelihood | Remediation Cost | Priority | Level |
|---|
PRE04-C |
low unlikely medium Automated Detection
...
Related Vulnerabilities
Search for vulnerabilities resulting from the violation of this rule on the CERT website.
Other Languages
...
Related Guidelines
...
...
...
References
...
Bibliography
...
...
...
...
...
...
PRE03-C. Prefer typedefs to defines for encoding types 01. Preprocessor (PRE) 
Image Added Image Added Image Modified
