Advertisement

The Fragile Base Class Problem and Its Impact on Component Systems

  • Leonid Mikhajlov
  • Emil Sekerinski
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 1357)

Abstract

In this paper we study applicability of the code inheritance mechanism to the domain of open component systems in light of so-called fragile base class problem. We propose a system architecture based on disciplined inheritance and present three check lists for component framework designers, component framework developers, and its users.

Keywords

Base Class Modus Cation Check List Extension Class Instance Variable 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    IBM Corporation. IBM’s System Object Model (SOM): Making Reuse a Reality. IBM Corporation, Object Technology Products Group, Austin, Texas. http://www.developer.ibm.com/library/ref/reference.html
  2. 2.
    Walter L. Hürsch. Should Superclass be Abstract? Proceedings ECOOP’94, M. Tokoro, R. Pareschi (Ed.), LNCS 821, Springer-Verlag, Bologna, Italy 1994, pp.12–31.Google Scholar
  3. 3.
    Gregor Kiczales, John Lamping. Issues in the design and specification of class libraries. OOPSLA’ 92 Proceedings, pp. 435–451, 1992.Google Scholar
  4. 4.
    Leonid Mikhajlov, Emil Sekerinski. The Fragile Base Class Problem and Its Solution. TUCS Technical Report No 117, Turku Centre for Computer Science, Turku, June 1997.Google Scholar
  5. 5.
    Cune Pfister, Clemens Szyperski. Oberon/F Framework. Tutorial and Reference. Oberon microsystems, Inc., 1994.Google Scholar
  6. 6.
    Dick Pountain, Clemens Szyperski. Extensible Software Systems. Byte Magazine, 19(5): 57–62, May 1994. http://www.byte.com/art/9405/sec6/art1.html.Google Scholar
  7. 7.
    Alan Snyder. Encapsulation and Inheritance in Object-Oriented Programming Languages. OOPSLA’ 86 Proceedings, pp.38–45, 1986.Google Scholar
  8. 8.
    Patric Steyaert, Carine Lucas, Kim Mens, Theo D’Hondt. Reuse Contracts: Managing the Evolution of Reusable Assets. OOPSLA’ 96 Proceedings, pp. 268–285, 1996.Google Scholar
  9. 9.
    Bjarne Stroustrup. The C++ Programming Language. Addison-Wesley, 1986.Google Scholar
  10. 10.
    David Taenzer, Murthy Gandi, Sunil Podar. Problems in Object-Oriented Software Reuse. In Proceedings ECOOP’89, S. Cook (Ed.), Cambridge University Press. Nottingham, July 10–14, 1989, pp.25–38.Google Scholar
  11. 11.
    S. Williams and C. Kinde. The Component Object Model: Technical Overview. Dr. Dobbs Journal, December 1994.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1998

Authors and Affiliations

  • Leonid Mikhajlov
    • 1
  • Emil Sekerinski
    • 1
  1. 1.Turku Centre for Computer ScienceTurkuFinland

Personalised recommendations