Linked by Thom Holwerda on Tue 30th Jan 2007 21:24 UTC, submitted by anonymous
General Development "While defensive programming effectively guarantees the condition of a method's input, it becomes repetitive if it is pervasive across a series of methods. 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."
Thread beginning with comment 207586
To read all comments associated with this story, please click here.
This problem was already solved
by Meor on Wed 31st Jan 2007 02:25 UTC
Meor
Member since:
2006-09-29

Same old problem different name. This is design by contract and it's been around since the mid 80s.

http://www.eiffel.com/developers/faqs/eiffel-language.html#classic-...

Reply Score: 1

sukru Member since:
2006-11-19

Same old problem different name. This is design by contract and it's been around since the mid 80s.

They already mentioned design by contract (There is a whole section on it). And AOP is an efficient way to enforce the contracts on Java language code.

(AOP is also very effective at other topics like logging, security, etc. If I were you, I'd not miss the reading).

Yet, not reading the linked article is understandable. But not reading the summary is way beyond.


add reusable validation constraints to your code using the power of AOP, design by contract, and a handy library called OVal."

Reply Parent Score: 1