Noncompliant Code Example
The following This noncompliant code example contains references to headers that may exist independently in various environments but can be ambiguously interpreted by a C-compliant compiler:
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-C-EX1: Although 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.
|Axivion Bauhaus Suite|
|[ISO/IEC 9899:2011]||Subclause 6.10.2, "Source File Inclusion"|