B. Meyer, Objcct-o'icntcd Softwa'c C'onst'uction, Prentice Hall, 1988  Home/Search   Document Not in Database   Summary   Related Articles

....is no preference rules that depend on the order of parents. This conservative approach allows more and simpler checks without forcing the compiler or human reader to look into the class bodies. In this way it promotes a separation between design (class interface) and implementation (class body) [17]. Naming conflicts that occur ;accidentally when large projects are merged can be solved by renaming where all occurences of a name including references calls are consistently replaced. However inheritance conflicts can only be solved by redefinition this way. One typically declares the ....

....and etsured assertions, respectively, and play different roles. The caller must guaran tee that the assertions at the begin of the definition (require) are satisfied. The implementor must guarantee those at the end (ensure) The advantage of this kind of programming with interfaces as contracts [17] is the separation of responsibilities, in particular, checks need not be built into the wrong program context avoiding the dreaded argument overcheck syndrome of many large modular programs where programs perform the same checks in many places and sometimes often in the same recursive ....

B. Meyer, Objcct-o'icntcd Softwa'c C'onst'uction, Prentice Hall, 1988

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC