Import is Not Inheritance - Why We Need Both: Modules and Classes

  title={Import is Not Inheritance - Why We Need Both: Modules and Classes},
  author={Clemens A. Szyperski},
The design of many popular object-oriented languages like Smalltalk, Eiffel, or Sather follows a certain trend: The class is the only structuring form. In this paper, the need for having modules besides classes is claimed. Modules stem from a different language family and at first glance it seems that they can easily be unified with classes. Among other things, unifying modules and classes carries the danger of unifying the import and inheritance relationships. Constructs in several languages… CONTINUE READING

From This Paper

Figures, tables, and topics from this paper.


Publications referenced by this paper.
Showing 1-10 of 30 references

Technical Report TR-91-34

  • S. M. Omohundro. The Sather Language
  • International Computer Science Institute…
  • 1991
Highly Influential
13 Excerpts


  • N. Wirth. Type Extensions.ACM Trans. Programming Languages, Systems
  • 204-214. July
  • 1988
Highly Influential
9 Excerpts

Eiffel Language)

  • B. Meyer. Object-Oriented Software Construction
  • Prentice-Hall, Englewood Cliffs, NJ.
  • 1988
Highly Influential
14 Excerpts

Structured Programming (was: Structured Language World)

  • L. Tesler. Object-PascalReport
  • 9:3, 10-17.
  • 1985
Highly Influential
4 Excerpts

Beginner’s Guide for the UCSD Pascal System

  • K. L. Bowles
  • Byte Books, Peterborough, NH.
  • 1980
Highly Influential
4 Excerpts


  • A.J
  • J.A. Goguen.OOZE: An Object-OrientedZ Environment…
  • 1991
1 Excerpt


  • U. Hölzle, C. Chambers
  • Ungar. Optimizing Dynamically-Typed Object…
  • 1991
1 Excerpt

Technical Report 156

  • R. Griesemer.On the Linearization of Graphs, Writing Symbol Files
  • Institutefor ComputerSystems,ETH Zurich…
  • 1991
1 Excerpt

Similar Papers

Loading similar papers…