Page: NUM00-J. Detect or prevent integer overflow
|
Jon O'Donnell |
Aug 06, 2021
|
Page: NUM01-J. Do not perform bitwise and arithmetic operations on the same data
|
Michal Rozenau |
May 18, 2021
|
Page: NUM02-J. Ensure that division and remainder operations do not result in divide-by-zero errors
|
Svyatoslav Razmyslov |
Jun 25, 2021
|
Page: NUM03-J. Use integer types that can fully represent the possible range of unsigned data
|
Carol J. Lallier |
Jun 03, 2015
|
Page: NUM04-J. Do not use floating-point numbers if precise computation is required
|
Michal Rozenau |
May 18, 2021
|
Page: NUM07-J. Do not attempt comparisons with NaN
|
Svyatoslav Razmyslov |
Jun 25, 2021
|
Page: NUM08-J. Check floating-point inputs for exceptional values
|
Michal Rozenau |
May 18, 2021
|
Page: NUM09-J. Do not use floating-point variables as loop counters
|
Valery |
Feb 08, 2024
|
Page: NUM10-J. Do not construct BigDecimal objects from floating-point literals
|
Svyatoslav Razmyslov |
Jun 25, 2021
|
Page: NUM11-J. Do not compare or inspect the string representation of floating-point values
|
David Svoboda |
Mar 13, 2024
|
Page: NUM12-J. Ensure conversions of numeric types to narrower types do not result in lost or misinterpreted data
|
David Svoboda |
Jan 18, 2022
|
Page: NUM13-J. Avoid loss of precision when converting primitive integers to floating-point
|
Jon O'Donnell |
Aug 06, 2021
|
Page: NUM14-J. Use shift operators correctly
|
Svyatoslav Razmyslov |
Apr 07, 2022
|
Page: NUM50-J. Convert integers to floating point for floating-point operations
|
Michal Rozenau |
Jan 10, 2023
|
Page: NUM51-J. Do not assume that the remainder operator always returns a nonnegative result for integral operands
|
Will Snavely |
Nov 16, 2017
|
Page: NUM52-J. Be aware of numeric promotion behavior
|
Will Snavely |
Nov 16, 2017
|
Page: NUM53-J. Use the strictfp modifier for floating-point calculation consistency across platforms
|
Will Snavely |
Nov 16, 2017
|
Page: NUM54-J. Do not use denormalized numbers
|
Will Snavely |
Nov 16, 2017
|