According to subclause 6.2.7 of the C Standard [ISO/IEC 9899:2011],
All declarations that refer to the same object or function shall have compatible type; otherwise, the behavior is undefined.
(See also undefined behavior 15 of Annex J.)
Further, according to subclause 126.96.36.199,
Any identifiers that differ in a significant character are different identifiers. If two identifiers differ only in nonsignificant characters, the behavior is undefined.
(See also undefined behavior 31 of Annex J.)
Identifiers in mutually visible scopes must be deemed unique by the compiler to prevent confusion about which variable or function is being referenced. Implementations can allow additional nonunique characters to be appended to the end of identifiers, making the identifiers appear unique while actually being indistinguishable.
It is reasonable for scopes that are not visible to each other to have duplicate identifiers. For example, two functions can each have a local variable with the same name because their scopes cannot access each other. But a function's local variable names should be distinct from each other as well as from all static variables declared within the function's file (and from all included header files.)
To guarantee that identifiers are unique, the number of significant characters recognized by the most restrictive compiler used must be determined. This assumption must be documented in the code.
The standard defines the following minimum requirements:
- 63 significant initial characters in an internal identifier or a macro name. (Each universal character name or extended source character is considered a single character.)
- 31 significant initial characters in an external identifier. (Each universal character name specifying a short identifier of 0000FFFF or less is considered 6 characters; each universal character name specifying a short identifier of 00010000 or more is considered 10 characters; and each extended source character, if any exist, is considered the same number of characters as the corresponding universal character name.)
Restriction of the significance of an external name to fewer than 255 characters in the standard (considering each universal character name or extended source character as a single character) is an obsolescent feature that is a concession to existing implementations. As a result, it is not necessary to comply with this restriction as long as the identifiers are unique and the assumptions concerning the number of significant characters are documented.
Noncompliant Code Example (Source Character Set)
On implementations that support only the minimum requirements for significant characters required by the standard, this code example is noncompliant because the first 31 characters of the external identifiers are identical:
Compliant Solution (Source Character Set)
In a compliant solution, the significant characters in each identifier must differ:
Noncompliant Code Example (Universal Character Names)
In this noncompliant code example, both external identifiers consist of four universal character names. Because the first three universal character names of each identifier are identical, both identify the same integer array on implementations that support only the minimum requirements for significant characters required by the standard:
Compliant Solution (Universal Character Names)
For portability, the first three universal character name combinations used in an identifier must be unique:
Nonunique identifiers can lead to abnormal program termination, denial-of-service attacks, or unintended information disclosure.
|Supported indirectly via|
|Axivion Bauhaus Suite|
Non-distinct identifiers: external names
Non-unique identifiers: external name
Global variable declared with different types
Can detect some violations of this rule but cannot flag violations involving universal names
|LDRA tool suite|
|Polyspace Bug Finder|
Rec. partially covered.
0627, 0776, 0777, 0778,
0779, 0789, 0791, 0793
|Supported indirectly via|
|SonarQube C/C++ Plugin|
|ISO/IEC TR 24772:2013||Choice of Clear Names [NAI]|
Identifier Name Reuse [YOW]
Rule 5.1 (required)
Subclause 6.2.7, "Compatible Type and Composite Type"