Abstract
The next stop on your journey to Objectropolis takes you from Inheritance to a place called Polymorphism.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
- 2.
Indeed, we already have seen the word static used as a qualifier to describe encapsulation units, constructors and destructors, classes and members of classes, realm, reference variable type, and design constraints.
- 3.
This is one of a few examples where the implementation of object-oriented capabilities in ABAP deviates from the Java model.
- 4.
One could argue that we could define these subroutines specific to the type of boat to be maneuvered, such as start_motor_boat and turn_sail_boat_right, but that only shifts to the caller the location of the conditional logic to make the determination of both the type of boat and its maneuver.
- 5.
Horst Keller and Sascha Krűger, ABAP Objects: An Introduction to Programming SAP Applications, Addison Wesley, 2002, p.294.
- 6.
We might consider the word redefinition, qualifying a methods statement of a subclass definition, as a word enabling polymorphic behavior; however, this qualifier may also be used in the absence of polymorphism.
- 7.
We shall see in a subsequent chapter that such method definitions can be provided in ways other than just through inheritance.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2017 James E. McDonough
About this chapter
Cite this chapter
McDonough, J.E. (2017). Polymorphism. In: Object-Oriented Design with ABAP. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-2838-8_6
Download citation
DOI: https://doi.org/10.1007/978-1-4842-2838-8_6
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-2837-1
Online ISBN: 978-1-4842-2838-8
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books