03. Numbers (NUM)

Guidelines

• Page:
  NUM00-J. Detect or prevent integer overflow
• Page:
  NUM01-J. Do not perform bitwise and arithmetic operations on the same data
• Page:
  NUM02-J. Ensure that division and remainder operations do not result in divide-by-zero errors
• Page:
  NUM03-J. Use integer types that can fully represent the possible range of unsigned data
• Page:
  NUM04-J. Do not use floating-point numbers if precise computation is required
• Page:
  NUM07-J. Do not attempt comparisons with NaN
• Page:
  NUM08-J. Check floating-point inputs for exceptional values
• Page:
  NUM09-J. Do not use floating-point variables as loop counters
• Page:
  NUM10-J. Do not construct BigDecimal objects from floating-point literals
• Page:
  NUM11-J. Do not compare or inspect the string representation of floating-point values
• Page:
  NUM12-J. Ensure conversions of numeric types to narrower types do not result in lost or misinterpreted data
• Page:
  NUM13-J. Avoid loss of precision when converting primitive integers to floating-point
• Page:
  NUM14-J. Use shift operators correctly
• Page:
  NUM50-J. Convert integers to floating point for floating-point operations
• Page:
  NUM51-J. Do not assume that the remainder operator always returns a nonnegative result for integral operands
• Page:
  NUM52-J. Be aware of numeric promotion behavior
• Page:
  NUM53-J. Use the strictfp modifier for floating-point calculation consistency across platforms
• Page:
  NUM54-J. Do not use denormalized numbers
• Page:
  Rec. 03. Numeric Types and Operations (NUM)
• Page:
  Rule 03. Numeric Types and Operations (NUM)

Risk Assessment Summary

FIO13-J. Do not rely on the write() method to output integers outside the range 0 to 255      The CERT Oracle Secure Coding Standard for Java      FLP00-J. Avoid using floating point numbers when precise computation is needed