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® 28.0w | AdaCore Inc |
An integer object is initialized directly from a string literal, whose array type is incompatible with the destination.
| Class Name | Bad Initializer Type |
|---|---|
| Significance | style |
| Mnemonic | PARSE.BAD.IT |
| Categories | None |
| Availability | Available for C and C++. |
| Enabling | Checks for this warning class are enabled by default.
However, warning instances of this class that are issued as parser
errors (rather than parser warnings)
will be discarded
when using factory configuration settings.
To prevent these instances from being discarded, add the
following WARNING_FILTER rule to the project configuration file.
WARNING_FILTER += allow class="Bad Initializer Type" WARNING_FILTER += discard class="Bad Initializer Type" |
char short_text[2] = "text"; /* 'Bad Initializer Type' warning issued here */ char fixed_text[] = "text"; /* ok: deduce space for all characters and the terminator */
To reproduce this example, analyze it with the following configuration:
WARNING_FILTER += allow class="Bad Initializer Type"
gcc -c -std=c11 example.c
The following configuration file parameters affect checks for this warning class.
To report problems with this documentation, please visit https://support.adacore.com/csm.