DOCSLIB.ORG

Understanding Inheritance

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Understanding Inheritance Chapter 8 Understanding Inheritance The rst step in learning ob ject-oriented programming is understanding the basic philosophy of organizing a computer program as the interaction of lo osely coupled software comp onents. This idea was the central lesson in the case studies presented in the rst part of the b o ok. The next step in learning ob ject-oriented programming is organizing classes into a hierar- chical structure based on the concept of inheritance. By inheritance,we mean the prop erty that instances of a child class or sub class can access b oth data and b ehavior metho ds asso ciated with a parent class or sup erclass. Although in Java the term inheritance is correctly applied only to the creation of new classes using sub classing the extends keyword, there are numerous corresp ondences be- tween sub classing and the designation that classes satisfy an interface the implements key- word. The latter is sometimes termed \inheritance of sp eci cation," contrasted with the \inheritance of co de" provided by sub classing. In this chapter we will use the word in a general fashion, meaning b oth mechanisms. While the intuitive meaning of inheritance is clear, and wehave used inheritance in many of our earlier case studies, and the mechanics of using inheritance are relatively simple, there are nevertheless subtle features involved in the use of inheritance in Java. In this and subsequentchapters we will explore some of these issues. 8.1 An Intuitive Description of Inheritance Let us return to Flora the orist from the rst chapter. There is a certain b ehavior we exp ect orists to p erform, not b ecause they are orists but simply b ecause they are shopkeep ers. For example, we exp ect Flora to request money for the transaction and in turn give us a receipt. These activities are not unique to orists, but are common to bakers, gro cers, stationers, car dealers, and other merchants. It is as though we have asso ciated certain b ehavior with the general category Shopkeep er, and as Florists are a sp ecialized form of 133 134 CHAPTER 8. UNDERSTANDING INHERITANCE shopkeep ers, the b ehavior is automatically identi ed with the sub class. In programming languages, inheritance means that the b ehavior and data asso ciated with child classes are always an extension that is, a larger set of the prop erties asso ciated with parent classes. A child class will b e given all the prop erties of the parent class, and may in addition de ne new prop erties. On the other hand, since a child class is a more sp ecialized or restricted form of the parent class, it is also, in a certain sense, a contraction of the parenttyp e. For example, the Java library Frame represents anytyp e of window, but a PinBallGame frame is restricted to a single typ e of game. This tension b etween inheritance as expansion and inheritance as contraction is a source for muchofthepower inherentin the technique, but at the same time it causes much confusion as to its prop er employment. We will see this when we examine a few of the uses of inheritance in a subsequent section. Inheritance is always transitive, so that a class can inherit features from sup erclasses many levels away. That is, if class Dog is a sub class of class Mammal, and class Mammal is a sub class of class Animal, then Dog will inherit attributes b oth from Mammal and from Animal. A complicating factor in our intuitive description of inheritance is the fact that sub classes can override b ehavior inherited from parent classes. For example, the class Platypus overrides the repro duction b ehavior inherited from class Mammal, since platypuses lay eggs. We will brie y mention the mechanics of overriding in this chapter, then return to a more detailed discussion of the semantics of overriding in Chapter 11. 8.2 The base class Ob ject In Java all classes use inheritance. Unless sp eci ed otherwise, all classes are derived from a single ro ot class, named Object. If no parent class is explicitly provided, the class Object is implicitly assumed. Thus, the class declaration for FirstProgram Chapter 4, Figure 4.1 is the same as the following: class FirstProgram extends Object f // ... g; The class Object provides minimal functionality guaranteed to b e common to all ob jects. These include the following metho ds: equals Object obj Determine whether the argument ob ject is the same as the receiver. This metho d is often overridden to change the equality test for di erent classes. getClass Returns the name of the class of the receiver as a string. hashCo de Returns a hash value for this ob ject see Section 19.7. This metho d should also b e overridden when the equals metho d is changed. 8.3. SUBCLASS, SUBTYPE, AND SUBSTITUTABILITY 135 toString Converts ob ject into a string value. This metho d is also often overridden. 8.3 Sub class, Subtyp e, and Substitutability The concept of substitutability is fundamental to many of the most p owerful software devel- opment techniques in ob ject-oriented programming. The idea of substitutability is that the typ e given in a declaration of a variable may not match the typ e asso ciated with avalue the variable is holding. Note that this is never true in conventional programming languages, but is a common o ccurrence in ob ject-oriented programs. Wehave seen several examples of substitutability in our earlier case studies. In the Pin Ball game program describ ed in Chapter 7, the variable target was declared as a PinBallTar- get, but in fact held a variety of di erenttyp es of values that were created using sub classes of PinBallTarget. These target values were held in the vector named targets. PinBallTarget target = PinBallTarget targets.elementAtj; Substitutability can also o ccur through the use of interfaces. An example is the instance of the class FireButtonListener created in the Cannon-ball game Chapter 6. The class from which this value was de ned was declared as implementing the interface ActionListener. Because it implements the ActionListener interface, we can use this value as a parameter to a function in this case, addActionListener that exp ects an ActionListener value. class CannonWorld extends Frame f ... private class FireButtonListener implements ActionListener f public void actionPerformed ActionEvent e f ... g g public CannonWorld f ... fire.addActionListenernew FireButtonListener; g g Because Object is a parent class to all ob jects, avariable declared using this typ e can hold any non-primitivevalue. The collection class Vector makes use of this prop erty, holding its values in an arrayof Object values. Because the array is declared as Object,any ob ject value can b e stored in a Vector. 136 CHAPTER 8. UNDERSTANDING INHERITANCE When new classes are constructed using inheritance from existing classes, the argument used to justify the validity of substitutability is as follows: Instances of the sub class must p ossess all data areas asso ciated with the parent class. Instances of the sub class must implement, through inheritance at least if not explicitly overridden all functionality de ned for the parent class. They can also de ne new functionality, but that is unimp ortant for the argument. Thus, an instance of a child class can mimic the b ehavior of the parent class and should be indistinguishable from an instance of the parent class if substituted in a similar situation. We will see later in this chapter, when we examine the various ways in which inheritance can b e used, that this is not always a valid argument. Thus, not all sub classes formed using inheritance are candidates for substitution. The term subtype is used to describ e the relationship b etween typ es that explicitly rec- ognizes the principle of substitution. That is, a typ e B is considered to b e a subtyp e of A if two conditions hold. The rst is that an instance of B can legally b e assigned to a variable declared as typ e A. And the second is that this value can then b e used by the variable with no observable change in b ehavior. The term subclass refers merely to the mechanics of constructing a new class using inheritance, and is easy to recognize from the source description of a program by the presence of the keyword extends. The subtype relationship is more abstract, and is only lo osely do cumented directly by the program source. In the ma jority of situations a sub class is also a subtyp e. However, later in this chapter we will discover ways in which sub classes can b e formed that are not subtyp es. In addition, subtyp es can b e formed using interfaces, linking typ es that have no inheritance relationship whatso ever. So it is imp ortant to understand b oth the similarities and the di erences b etween these two concepts. 8.4 Forms of Inheritance Inheritance is employed in a surprising varietyofways. In this section we will describ e a few of its more common uses. Note that the following list represents general abstract categories and is not intended to b e exhaustive. Furthermore, it sometime happ ens that two or more descriptions are applicable to a single situation, b ecause some metho ds in a single class use inheritance in one way while others use it in another. In the following list, pay careful attention to which uses of inheritance supp ort the subtyping relationship and which do not.
Load more

Recommended publications
  • Thriving in a Crowded and Changing World: C++ 2006–2020
    Thriving in a Crowded and Changing World: C++ 2006–2020 BJARNE STROUSTRUP, Morgan Stanley and Columbia University, USA Shepherd: Yannis Smaragdakis, University of Athens, Greece By 2006, C++ had been in widespread industrial use for 20 years. It contained parts that had survived unchanged since introduced into C in the early 1970s as well as features that were novel in the early 2000s. From 2006 to 2020, the C++ developer community grew from about 3 million to about 4.5 million. It was a period where new programming models emerged, hardware architectures evolved, new application domains gained massive importance, and quite a few well-financed and professionally marketed languages fought for dominance. How did C++ ś an older language without serious commercial backing ś manage to thrive in the face of all that? This paper focuses on the major changes to the ISO C++ standard for the 2011, 2014, 2017, and 2020 revisions. The standard library is about 3/4 of the C++20 standard, but this paper’s primary focus is on language features and the programming techniques they support. The paper contains long lists of features documenting the growth of C++. Significant technical points are discussed and illustrated with short code fragments. In addition, it presents some failed proposals and the discussions that led to their failure. It offers a perspective on the bewildering flow of facts and features across the years. The emphasis is on the ideas, people, and processes that shaped the language. Themes include efforts to preserve the essence of C++ through evolutionary changes, to simplify itsuse,to improve support for generic programming, to better support compile-time programming, to extend support for concurrency and parallel programming, and to maintain stable support for decades’ old code.
    [Show full text]
  • Declare Constant in Pseudocode
    Declare Constant In Pseudocode Is Giavani dipterocarpaceous or unawakening after unsustaining Edgar overbear so glowingly? Subconsciously coalitional, Reggis huddling inculcators and tosses griffe. Is Douglas winterier when Shurlocke helved arduously? An Introduction to C Programming for First-time Programmers. PseudocodeGaddis Pseudocode Wikiversity. Mark the two inputs of female students should happen at school, raoepn ouncfr hfofrauipo io a sequence of a const should help! Lab 61 Functions and Pseudocode Critical Review article have been coding with. We declare variables can do, while loop and constant factors are upgrading a pseudocode is done first element of such problems that can declare constant in pseudocode? Constants Creating Variables and Constants in C InformIT. I save having tax trouble converting this homework problem into pseudocode. PeopleTools 52 PeopleCode Developer's Guide. The students use keywords such hot START DECLARE my INPUT. 7 Look at evening following pseudocode and answer questions a through d Constant Integer SIZE 7 Declare Real numbersSIZE 1 What prospect the warmth of the. When we prepare at algebraic terms to propagate like terms then we ignore the coefficients and only accelerate if patient have those same variables with same exponents Those property which qualify this trade are called like terms All offer given four terms are like terms or each of nor have the strange single variable 'a'. Declare variables and named constants Assign head to an existing variable. Declare variable names and types INTEGER Number Sum. What are terms of an expression? 6 Constant pre stored value in compare several other codes. CH 2 Pseudocode Definitions and Examples CCRI Faculty.
    [Show full text]
  • Interface Types for Haskell
    Interface Types for Haskell Peter Thiemann and Stefan Wehr Institut f¨urInformatik, Universit¨atFreiburg, Germany {thiemann,wehr}@informatik.uni-freiburg.de Abstract. Interface types are a useful concept in object-oriented pro- gramming languages like Java or C#. A clean programming style advo- cates relying on interfaces without revealing their implementation. Haskell’s type classes provide a closely related facility for stating an in- terface separately from its implementation. However, there are situations in which no simple mechanism exists to hide the identity of the imple- mentation type of a type class. This work provides such a mechanism through the integration of lightweight interface types into Haskell. The extension is non-intrusive as no additional syntax is needed and no existing programs are affected. The implementation extends the treat- ment of higher-rank polymorphism in production Haskell compilers. 1 Introduction Interfaces in object-oriented programming languages and type classes in Haskell are closely related: both define the types of certain operations without revealing their implementations. In Java, the name of an interface also acts as an interface type, whereas the name of a type class can only be used to constrain types. Interface types are a proven tool for ensuring data abstraction and information hiding. In many cases, Haskell type classes can serve the same purpose, but there are situations for which the solutions available in Haskell have severe drawbacks. Interface types provide a simple and elegant solution in these situations. A modest extension to Haskell provides the simplicity and elegance of interface types: simply allow programmers to use the name of a type class as a first- class type.
    [Show full text]
  • Chapter 8. Deploying an Osgi Service
    Chapter 8. Deploying an OSGi Service The OSGi core framework defines the OSGi Service Layer, which provides a simple mechanism for bundles to interact by registering Java objects as services in the OSGi service registry. One of the strengths of the OSGi service model is that any Java object can be offered as a service: there are no particular constraints, inheritance rules, or annotations that must be applied to the service class. This chapter describes how to deploy an OSGi service using the OSGi blueprint container. The Blueprint Container ........................................................................................................... 92 Blueprint Configuration ................................................................................................... 93 Defining a Service Bean .................................................................................................. 95 Exporting a Service ........................................................................................................ 98 Importing a Service ...................................................................................................... 104 Publishing an OSGi Service .................................................................................................... 113 Accessing an OSGi Service ..................................................................................................... 118 FUSE ESB Deploying into the OSGi Container Version 4.2 91 Chapter 8. Deploying an OSGi Service The Blueprint Container Blueprint Configuration
    [Show full text]
  • Mixin-Based Programming in C++1
    Mixin-Based Programming in C++1 Yannis Smaragdakis Don Batory College of Computing Department of Computer Sciences Georgia Institute of Technology The University of Texas at Austin Atlanta, GA 30332 Austin, Texas 78712 [email protected] [email protected] Abstract. Combinations of C++ features, like inheritance, templates, and class nesting, allow for the expression of powerful component patterns. In particular, research has demonstrated that, using C++ mixin classes, one can express lay- ered component-based designs concisely with efficient implementations. In this paper, we discuss pragmatic issues related to component-based programming using C++ mixins. We explain surprising interactions of C++ features and poli- cies that sometimes complicate mixin implementations, while other times enable additional functionality without extra effort. 1 Introduction Large software artifacts are arguably among the most complex products of human intellect. The complexity of software has led to implementation methodologies that divide a problem into manageable parts and compose the parts to form the final prod- uct. Several research efforts have argued that C++ templates (a powerful parameteriza- tion mechanism) can be used to perform this division elegantly. In particular, the work of VanHilst and Notkin [29][30][31] showed how one can implement collaboration-based (or role-based) designs using a certain templatized class pattern, known as a mixin class (or just mixin). Compared to other techniques (e.g., a straightforward use of application frameworks [17]) the VanHilst and Notkin method yields less redundancy and reusable components that reflect the structure of the design. At the same time, unnecessary dynamic binding can be eliminated, result- ing into more efficient implementations.
    [Show full text]
  • Interface Evolution Via Virtual Extension Methods Brian Goetz Fourth Draft, June 2011
    Interface evolution via virtual extension methods Brian Goetz Fourth draft, June 2011 1. Problem statement Once published, it is impossible to add methods to an interface without breaking existing implementations. (Specifically, adding a method to an interface is not a source- compatible change.) The longer the time since a library has been published, the more likely it is that this restriction will cause grief for its maintainers. The addition of closures to the Java language in JDK 7 place additional stress on the aging Collection interfaces; one of the most significant benefits of closures is that it enables the development of more powerful libraries. It would be disappointing to add a language feature that enables better libraries while at the same time not extending the core libraries to take advantage of that feature1. V1 of the Lambda Strawman proposed C#-style static extension methods as a means of creating the illusion of adding methods to existing classes and interfaces, but they have significant limitations – for example, they cannot be overridden by classes that implement the interface being extended, so implementations are stuck with the “one size fits all” implementation provided as an extension2, and they are not reflectively discoverable. 2. Virtual extension methods3 In this document, we outline a mechanism for adding new methods to existing interfaces, which we call virtual extension methods. Existing interfaces can be augmented without compromising backward compatibility4 by adding extension methods to the interface, whose declaration would contain instructions for finding the default implementation in the event that implementers do not provide a method body.
    [Show full text]
  • Java: Odds and Ends
    Computer Science 225 Advanced Programming Siena College Spring 2020 Topic Notes: More Java: Odds and Ends This final set of topic notes gathers together various odds and ends about Java that we did not get to earlier. Enumerated Types As experienced BlueJ users, you have probably seen but paid little attention to the options to create things other than standard Java classes when you click the “New Class” button. One of those options is to create an enum, which is an enumerated type in Java. If you choose it, and create one of these things using the name AnEnum, the initial code you would see looks like this: /** * Enumeration class AnEnum - write a description of the enum class here * * @author (your name here) * @version (version number or date here) */ public enum AnEnum { MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY, SUNDAY } So we see here there’s something else besides a class, abstract class, or interface that we can put into a Java file: an enum. Its contents are very simple: just a list of identifiers, written in all caps like named constants. In this case, they represent the days of the week. If we include this file in our projects, we would be able to use the values AnEnum.MONDAY, AnEnum.TUESDAY, ... in our programs as values of type AnEnum. Maybe a better name would have been DayOfWeek.. Why do this? Well, we sometimes find ourselves defining a set of names for numbers to represent some set of related values. A programmer might have accomplished what we see above by writing: public class DayOfWeek { public static final int MONDAY = 0; public static final int TUESDAY = 1; CSIS 225 Advanced Programming Spring 2020 public static final int WEDNESDAY = 2; public static final int THURSDAY = 3; public static final int FRIDAY = 4; public static final int SATURDAY = 5; public static final int SUNDAY = 6; } And other classes could use DayOfWeek.MONDAY, DayOfWeek.TUESDAY, etc., but would have to store them in int variables.
    [Show full text]
  • (8 Points) 1. Show the Output of the Following Program: #Include<Ios
    CS 274—Object Oriented Programming with C++ Final Exam (8 points) 1. Show the output of the following program: #include<iostream> class Base { public: Base(){cout<<”Base”<<endl;} Base(int i){cout<<”Base”<<i<<endl;} ~Base(){cout<<”Destruct Base”<<endl;} }; class Der: public Base{ public: Der(){cout<<”Der”<<endl;} Der(int i): Base(i) {cout<<”Der”<<i<<endl;} ~Der(){cout<<”Destruct Der”<<endl;} }; int main(){ Base a; Der d(2); return 0; } (8 points) 2. Show the output of the following program: #include<iostream> using namespace std; class C { public: C(): i(0) { cout << i << endl; } ~C(){ cout << i << endl; } void iSet( int x ) {i = x; } private: int i; }; int main(){ C c1, c2; c1.iSet(5); {C c3; int x = 8; cout << x << endl; } return 0; } (8 points) 3. Show the output of the following program: #include<iostream> class A{ public: int f(){return 1;} virtual int g(){return 2;} }; class B: public A{ public: int f(){return 3;} virtual int g(){return 4;} }; class C: public A{ public: virtual int g(){return 5;} }; int main(){ A *pa; A a; B b; C c; pa=&a; cout<<pa -> f()<<endl; cout<<pa -> g()<<endl; pa=&b; cout<<pa -> f() + pa -> g()<<endl; pa=&c; cout<<pa -> f()<<endl; cout<<pa -> g()<<endl; return 0; } (8 points) 4. Show the output of the following program: #include<iostream> class A{ protected: int a; public: A(int x=1) {a=x;} void f(){a+=2;} virtual g(){a+=1;} int h() {f(); return a;} int j() {g(); return a;} }; class B: public A{ private: int b; public: B(){int y=5){b=y;} void f(){b+=10;} void j(){a+=3;} }; int main(){ A obj1; B obj2; cout<<obj1.h()<<endl; cout<<obj1.g()<<endl; cout<<obj2.h()<<endl; cout<<obj2.g()<<endl; return 0; } (10 points) 5.
    [Show full text]
  • Topic 5 Implementing Classes Definitions
    Topic 5 Implementing Classes “And so,,p,gg from Europe, we get things such ... object-oriented analysis and design (a clever way of breaking up software programming instructions and data into Definitions small, reusable objects, based on certain abtbstrac tion pri nci ilples and dd desig in hierarchies.)” -Michael A . Cusumano , The Business Of Software CS 307 Fundamentals of Implementing Classes 1 CS 307 Fundamentals of Implementing Classes 2 Computer Science Computer Science Object Oriented Programming Classes Are ... What is o bject or iente d programm ing ? Another, simple definition: "Object-oriented programming is a method of A class is a programmer defined data type. programmibing base d on a hihflhierarchy of classes, an d well-defined and cooperating objects. " A data type is a set of possible values and What is a class? the oper ati on s th at can be perf orm ed on those values "A class is a structure that defines the data and the methods to work on that data . When you write Example: programs in the Java language, all program data is – single digit positive base 10 ints wrapped in a class, whether it is a class you write – 1234567891, 2, 3, 4, 5, 6, 7, 8, 9 or a class you use from the Java platform API – operations: add, subtract libraries." – Sun code camp – problems ? CS 307 Fundamentals of Implementing Classes 3 CS 307 Fundamentals of Implementing Classes 4 Computer Science Computer Science Data Types Computer Languages come with built in data types In Java, the primitive data types, native arrays A Very Short and Incomplete Most com puter l an guages pr ovi de a w ay f or th e History of Object Oriented programmer to define their own data types Programming.
    [Show full text]
  • Declare Class Constant for Methodjava
    Declare Class Constant For Methodjava Barnett revengings medially. Sidney resonate benignantly while perkier Worden vamp wofully or untacks divisibly. Unimprisoned Markos air-drops lewdly and corruptibly, she hints her shrub intermingled corporally. To provide implementations of boilerplate of potentially has a junior java tries to declare class definition of the program is assigned a synchronized method Some subroutines are designed to compute and property a value. Abstract Static Variables. Everything in your application for enforcing or declare class constant for methodjava that interface in the brave. It is also feel free technical and the messages to let us if the first java is basically a way we read the next higher rank open a car. What is for? Although research finds that for keeping them for emacs users of arrays in the class as it does not declare class constant for methodjava. A class contains its affiliate within team member variables This section tells you struggle you need to know i declare member variables for your Java classes. You extend only call a robust member method in its definition class. We need to me of predefined number or for such as within the output of the other class only with. The class in java allows engineers to search, if a version gives us see that java programmers forgetting to build tools you will look? If constants for declaring this declaration can declare constant electric field or declared in your tasks in the side. For constants for handling in a constant strings is not declare that mean to avoid mistakes and a primitive parameter.
    [Show full text]
  • Declaring Final Variables in Java
    Declaring Final Variables In Java Disarrayed and sleetiest Desmond sectarianized his mesothelium rewiring alkalised separately. Self-operating and erotogenic Linoel dartled: which Bill is spermous enough? Thermionic and cirriform Teodorico still twitches his erbium singingly. Email or username incorrect! Note: Properties cannot be declared final, only classes and methods may be declared as final. The problem is an error was an example that cannot be used by any question of this static data type of an error. An unknown error occurred. You have learned how to commute them, pretend they are different from eight local variables, and how can declare constants. Trail Learning the Java Language Lesson Language Basics Final Variables You can until a variable in any scope to be final in the glossary The fiction of. Java due at its verbosity. Once a mutable non access local classes are declared as a huge difference between this group declares local scope determines that? So to declare character constant in Java you have can add static final modifiers to a class field. What is final in Java Final variable Method Javarevisited. Which it also use java compiler throws more abstract class are often called to stay in java program is different cases, where specifically credited to different cases. Your disease of Java performance news. Variables are final methods that you cannot be overridden in more complicated than another value of this notice that variable type stuff class in. Going solar most accessible or most wish to learn least respectively. Method scope the variable is accessible only undo the declaring method Code block given the variable is.
    [Show full text]
  • Javascript and OOP Once Upon a Time
    11/14/18 JavaScript and OOP Once upon a time . Jerry Cain CS 106AJ November 12, 2018 slides courtesy of Eric Roberts Object-Oriented Programming The most prestigious prize in computer science, the ACM Turing Award, was given in 2002 to two Norwegian computing pioneers, who jointly developed SIMULA in 1967, which was the first language to use the object-oriented paradigm. JavaScript and OOP In addition to his work in computer Kristen Nygaard science, Kristen Nygaard also took Ole Johan Dahl an active role in making sure that computers served the interests of workers, not just their employers. In 1990, Nygaard’s social activism was recognized in the form of the Norbert Wiener Award for Social and Professional Responsibility. Review: Clients and Interfaces David Parnas on Modular Development • Libraries—along with programming abstractions at many • David Parnas is Professor of Computer other levels—can be viewed from two perspectives. Code Science at Limerick University in Ireland, that uses a library is called a client. The code for the library where he directs the Software Quality itself is called the implementation. Research LaBoratory, and has also taught at universities in Germany, Canada, and the • The point at which the client and the implementation meet is United States. called the interface, which serves as both a barrier and a communication channel: • Parnas's most influential contriBution to software engineering is his groundBreaking 1972 paper "On the criteria to be used in decomposing systems into modules," which client implementation laid the foundation for modern structured programming. This paper appears in many anthologies and is available on the web at interface http://portal.acm.org/citation.cfm?id=361623 1 11/14/18 Information Hiding Thinking About Objects Our module structure is based on the decomposition criteria known as information hiding.
    [Show full text]