Defensive Programming and Assertions

Defensive Programming and Assertions

📘 Overview Defensive programming anticipates invalid inputs and failure conditions to prevent incorrect program behavior. Assertions detect violated internal assumptions during development, while runtime validation handles conditions that can occur during normal execution.

🧠 Key Idea Validate conditions that callers or external systems can violate; assert conditions that correct program logic should guarantee. Assertions do not replace input validation or error handling.

⚔️ Core Details: - Boundary validation checks external data before use, including input types, permitted ranges, required fields, and collection bounds. - An assertion evaluates a Boolean condition and signals a programming defect if the condition is false. - Design by contract specifies preconditions before an operation, postconditions after successful completion, and invariants at defined program boundaries. - Public API preconditions require runtime checks when untrusted callers can violate them. - Assertions may be disabled in some execution environments; their conditions must not perform operations required for correctness. - Error handling uses mechanisms such as exceptions or explicit error results to report anticipated failures without silently continuing with invalid state.

🎯 Why It Matters: - Early validation prevents malformed data from propagating into harder-to-diagnose failures. - Assertions localize defects near the first violated assumption rather than a later visible symptom. - Explicit failure behavior makes interfaces more predictable and reduces the risk of corrupted program state. - Separating programmer defects from expected failures improves debugging and supports meaningful automated tests.

🧠 Quick Recall: - Defensive programming - anticipating misuse and failure conditions through explicit checks and controlled responses. - Assertion - an executable check of a condition expected to hold in a correct program. - Precondition - a requirement that must hold before an operation begins. - Postcondition - a guarantee that must hold after an operation completes successfully. - Invariant - a property maintained at specified points, such as loop boundaries or public method entry and exit.