ACM Home Page
Please provide us with feedback. Feedback
Function preconditions in object oriented software
Full text PdfPdf (397 KB)
Source ACM SIGPLAN Notices archive
Volume 26 ,  Issue 10  (October 1991) table of contents
Pages: 13 - 18  
Year of Publication: 1991
ISSN:0362-1340
Author
Jean Pierre LeJacq  Paradigm Software, 34 Millstone Drive, Marlborough, CT
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 4,   Downloads (12 Months): 16,   Citation Count: 1
Additional Information:

abstract   references   cited by   index terms  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/122616.122619
What is a DOI?

ABSTRACT

Functions in nonobject oriented languages are typically designed to minimize any preconditions which must be satisfied before the function can be legally called. In object oriented languages this prescription can reduce the refinement of the function through derivation. A tradeoff must be made between refinement potential, efficiency, and risk of incorrect usage.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
[1] Marshall P. Cline and Doug Lea. Using annotated C++. In C++ at Work '90, pages 65-71, Secaucus, NJ, U.S.A., September 1990. The Wang Institute of Boston University, The C++ Report.
 
2
 
3
[3] Andrew Koenig and Bjarne Stroustrup. Exception handling for C++ (revised). In 1990 USENIX C++ conference, pages 149-176, San Francisco, CA, U.S.A., April 1990. USENIX Association.
4
 
5
[5] Jean Pierre LeJacq. Semantic based design guidelines for object oriented programs. Journal of Object-Oriented Programming-focus on analysis & design, June 1991.
 
6
 
7
 
8
[8] Bjarne Stroustrup. Sixteen ways to stack a cat, part 2. The C++ report, 2(10):15-18, November 1990.
9
 
10