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
C and C++


PARSE.BAD.ICL : Bad Integral Compound Literal

Summary

A compound literal appears in an expression that requires an integral constant value, such as an enumeration initializer.

Properties

Class Name Bad Integral Compound Literal
Significance style
Mnemonic PARSE.BAD.ICL
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 Integral Compound Literal"
To disable checks for this warning class, add the following WARNING_FILTER rule to the project configuration file.
WARNING_FILTER += discard class="Bad Integral Compound Literal"

Example

enum Value {
    result = (int){1} // 'Bad Integral Compound Literal' warning issued here
};

enum FixedValue {
    fixed_result = 1 // ok: the enumerator uses an integral constant expression
};

To reproduce this example, analyze it with the following configuration:

WARNING_FILTER += allow class="Bad Integral Compound Literal"
# GNU 5 uses the standard integral-constant-expression path in C++98.
COMPILER_MODELS += g++ -> gpp:64.50000.1.0
g++ -c -std=gnu++98 example.cpp

Relevant Configuration File Parameters

The following configuration file parameters affect checks for this warning class.

 

To report problems with this documentation, please visit https://support.adacore.com/csm.