 
                            ...
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:
| Code Block | ||
|---|---|---|
| 
 | ||
| 
extern int *global_symbol_definition_lookup_table_a;
extern int *global_symbol_definition_lookup_table_b;
 | 
...
In a compliant solution, the significant characters in each identifier must differ.
| Code Block | ||
|---|---|---|
| 
 | ||
| 
extern int *a_global_symbol_definition_lookup_table;
extern int *b_global_symbol_definition_lookup_table;
 | 
Noncompliant Code Example (Universal
...
Character Names)
In this noncompliant code example, both external identifiers consist of four universal characterscharacter names. Because the first three universal characters character names of each identifier are identical, both identify the same integer array.
| Code Block | ||
|---|---|---|
| 
 | ||
| 
extern int *\U00010401\U00010401\U00010401\U00010401;
extern int *\U00010401\U00010401\U00010401\U00010402;
 | 
Compliant Solution (Universal
...
Character Names)
For portability, the first three universal character name combination used in an identifier must be unique.
| Code Block | ||
|---|---|---|
| 
 | ||
| 
extern int *\U00010401\U00010401\U00010401\U00010401;
extern int *\U00010402\U00010401\U00010401\U00010401;
 | 
...