2. Defensive Programming

Defensive Programming: Introduction

• Page:
  CON52-J. Document thread-safety and use annotations where applicable
• Page:
  DCL53-J. Minimize the scope of variables
• Page:
  DCL56-J. Do not attach significance to the ordinal associated with an enum
• Page:
  DCL58-J. Enable compile-time type checking of variable arity parameter types
• Page:
  DCL59-J. Do not apply public final to constants whose value might change in later releases
• Page:
  DCL60-J. Avoid cyclic dependencies between packages
• Page:
  ERR51-J. Prefer user-defined exceptions over more general exception types
• Page:
  ERR53-J. Try to gracefully recover from system errors
• Page:
  FIO51-J. Identify files using multiple file attributes
• Page:
  IDS50-J. Use conservative file naming conventions
• Page:
  MET54-J. Always provide feedback about the resulting value of a method
• Page:
  MSC50-J. Minimize the scope of the @SuppressWarnings annotation
• Page:
  MSC53-J. Carefully design interfaces before releasing them
• Page:
  NUM52-J. Be aware of numeric promotion behavior
• Page:
  OBJ51-J. Minimize the accessibility of classes and their members
• Page:
  OBJ52-J. Write garbage-collection-friendly code