Safely creating correct subclasses without seeing superclass code

Authors:
Clyde D. Ruby
Affiliations:
Department of Computer Science, Iowa State University, Ames, Iowa
Venue:
OOPSLA '00 Addendum to the 2000 proceedings of the conference on Object-oriented programming, systems, languages, and applications (Addendum)
Year:
2000

Citing 5
Cited 0

Abstraction and specification in program development

Abstraction and specification in program development
Component software: beyond object-oriented programming

Component software: beyond object-oriented programming
Safely creating correct subclasses without seeing superclass code

OOPSLA '00 Proceedings of the 15th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Applying "Design by Contract"

Computer
A Study of The Fragile Base Class Problem

ECCOP '98 Proceedings of the 12th European Conference on Object-Oriented Programming

Quantified Score

Hi-index	0.00

Visualization

Abstract

A major problem for object-oriented frameworks and class libraries is how to provide enough information about an extensible superclass so that programmers can safely create new subclasses without studying superclass code. The goal of my work is to determine what information is needed so library providers do not have to give away the code of library superclasses. A closely related goal is to provide guidelines that simplify reasoning about classes that inherit from such frameworks and class libraries. The long-term goal of my research is to develop tool support to automatically generate some of the necessary documentation and to assist programmers in reasoning about how to create correct subclasses.