• OOP requires the programmer to know too many details about object and method names and implementations.

• OOP requires application data to conform to conventions of the generic procedures:
  • OOP requires an object to be a member of a class rather than be viewable as a member.

  • Some OOP systems automatically include slots of supers in all their descendants. This inhibits use of different representations.

  • An object cannot be a member of a class in more than one way.

  • No single definition of an object is likely to encompass all possible uses (or if it did, it would be too big for typical uses).

  • Uses of an object with different superclasses are likely to conflict.

• OOP is often slow in execution.

Contents    Page-10    Prev    Next    Page+10    Index