JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.
If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.
If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.
| CodeSonar® 9.2p0 | CONFIDENTIAL | CodeSecure Inc |
Some elements of an object are initialized with designators, but some are initialized without designators.
See also Partially Uninitialized Aggregate.
| Class Name | Inconsistent Chained Designator Initialization | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Significance | style | ||||||||||||
| Mnemonic | LANG.STRUCT.INIT.ICDI | ||||||||||||
| Categories |
|
||||||||||||
| Availability | Available for C and C++. |
||||||||||||
| Enabling | Checks for this warning class are disabled by default,
and require the unnormalized
C ASTs for the project. To enable them, add the following
WARNING_FILTER rule and RETAIN_UNNORMALIZED_C_AST specification to the project configuration file.
RETAIN_UNNORMALIZED_C_AST = Yes WARNING_FILTER += allow class="Inconsistent Chained Designator Initialization" |
struct S { int x; int y; };
struct T {
int w;
struct S s;
int z;
};
struct T t1 = { /* 'Inconsistent Chained Designator Initialization' warning issued here
* - fields .w and .s.y are initialized without designators
* - 'Partially Uninitialized Aggregate' warning also issued if enabled,
* because field .z is not initialized at all
*/
1,
.s.x = 2,
3, /* a human reader may assume that this initializes .z but it
* actually initializes .s.y, as if the initialization of t1
* was written { 1, { 2, 3 }, 0 }
*/
};
struct T t2 = { /* ok: all fields initialized with designators */
.w = 1,
.s = {2, 3},
.z = 4,
};
struct T t3 = { 1, {2,3}, 4 }; /* ok: no fields initialized without designators */
The following configuration file parameters affect checks for this warning class.
To report problems with this documentation, please visit https://support.codesecure.com/.