Consider the following class hierarchy. class A { } int a = 0; int f (int x) {...} int g (int x) {...} class B extends A { int b = 7; int f (int x) { ... } } Explain how a compiler stores objects of classes A and B in memory. What are the key challenges in the compilation of such class hierarchies (about accessing member variables and invoking methods)? How does the layout that you describe solve these problems? You may want to use appropriate diagrams to illustrate your answer.

Specify, design, and implement a class called statistician.  After a statistician is initialized, it can be given a sequence of double numbers.  Each number in the sequence is given to the statistician by activating a member function called next_number.  For example, we can declare a statistician called s, and then give it the sequence of numbers 1.1, -2.4, 0.8 as shown here: statistician s; s.next_number(1.1); s.next_number(-2.4); s.next_number(0.8);       After a sequence has been given to a statistician, there are various member functions to obtain information about the sequence.  Include member functions that will provide the length of the sequence, the last number of the sequence, the sum of all the numbers in the sequence, the arithmetic mean of the numbers(i.e the sum of the numbers divided by the length of the sequence), the smallest number in the sequence, and the largest number in the sequence.  Notice that the length and sum functions can be called at any time, even if there…

Implement a nested class composition relationship between any two class types from the following list: Advisor Вook Classroom Department Friend Grade School Student Teacher Tutor Write all necessary code for both classes to demonstrate a nested composition relationship including the following: a. one encapsulated data member for each class b. inline default constructor using constructor delegation for each class c. inline one-parameter constructor for each class d. inline accessors for all data members e. inline mutators for all data members

A subclass of an abstract class must provide concrete implementations for each of the parent class's abstract methods in order to be considered a subclass. What are your thoughts on this?