In pursuit of code quality, Defensive programming with AOP
OVal takes the legwork out of writing repetitive conditionals
From the developerWorks archives
Date archived: December 19, 2016 | First published: January 30, 2007
While defensive programming effectively guarantees the condition of a method's input, it becomes repetitive if it is pervasive across a series of methods. This month, Andrew Glover shows you an easier way to add reusable validation constraints to your code using the power of AOP, design by contract, and a handy library called OVal.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.