...
Automated detection of narrowing conversions on integral types is straightforward. Determining whether such conversions correctly reflect the intent of the programmer is infeasible in the general case. Heuristic warnings could be useful.
Related Guidelines
"INT31-C. Ensure that integer conversions do not result in lost or misinterpreted data" | ||||
| "FLP34-C. Ensure that floating point conversions are within range of the new type" | |||
"INT31-CPP. Ensure that integer conversions do not result in lost or misinterpreted data" | ||||
| "FLP34-CPP. Ensure that floating point conversions are within range of the new type" | |||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="f2f4c6fc2c968fed-e93c32d3-48bd4dea-8285ae45-3eaa4f0fe7983361f2676d56"><ac:plain-text-body><![CDATA[ | [ISO/IEC TR 24772:2010 | http://www.aitcnet.org/isai/] | "Numeric Conversion Errors [FLC]" | ]]></ac:plain-text-body></ac:structured-macro> |
CWE ID 681, "Incorrect Conversion between Numeric Types" | ||||
| CWE ID 197, "Numeric Truncation Error" |
...