第一章对象入门1.5-1.6(java编程思想第四版)（The first chapter introduction object 1.5-1.6 (Java programming fourth edition)）.docVIP

第一章对象入门1.5-1.6(java编程思想第四版)（The first chapter introduction object 1.5-1.6 (Java programming fourth edition)） 1.5 inheritance: reuse the interface 1.5.1 improves base classes 1.5.2 equivalence and similar relations 1.6 interchangeable use of polymorphic objects 1.6.1 dynamic binding 1.6.2 abstract base classes and interfaces 1.5 inheritance: reuse the interface As for itself, the concept of object can bring us great convenience. It conceptually allows us to encapsulate a wide variety of data and functionality together. In this way, the concept of problem space can be properly expressed without deliberately following the basic machine expression. In programming languages, these concepts are represented as concrete data types (using the class keyword). It would be frustrating if we tried to make a data type, and if we had to create a new type to make it about the same function. But if we can make use of the existing data type, clone it, and then add and modify it according to the situation, the situation will be much more ideal. Inheritance is designed for this goal. But inheritance is not entirely equivalent to cloning. In the process of succession, if the original class (officially called the base class, super class or superclass) changes, the revised clone class (officially called inheritance or Zi Lei) will also reflect this change. In Java, inheritance is achieved through the extends keyword When using inheritance, it is equivalent to creating a new class. This new class contains not only all the members of the existing type (although the private members are hidden and inaccessible), but more importantly, it copies the interface of the underlying class. That is, all messages that can be sent to objects of the underlying class can also be sent to the object of the derived class as they were. We can know the class type based on the messages that can be sent. This means that the derived class has the same type as the underlying class! To really understand the implica