Answer the questions (i) to (iii) based on the following: class Furniture(object): #Line 1 def _init_(self,Q):

Question 96 of 97

Q. Answer the questions

(i) to

(iii) based on the following: class Furniture(object): #Line 1 def init(self,Q): #Line 2 self.Qty = Q def GetMore(self,TQ): #Line 3 self.Qty =self.Qty+TQ def FRDisp(self): #Line 4 print self.Qty class Fixture(object): #Line 5 def init(self,TQ): #Line 6 self.Qty=TQ def GetMore(self,TQ): #Line 7 self.Qty =self.Qty+TQ def FXDisp(self): #Line 8 print self.Qty class Flat(Furniture,Fixture): #Line 9 def init(self,fno): #Line 10 self.Fno=fno Q=0 if self.Fno<100: Q=10 else: Q=20 Furniture.init(self,Q): #Line 11 Fixture.init(self,Q): #Line 12 def More(self,Q): #Line 13 Furniture.GetMore(self,Q) Fixture.GetMore(self,Q) def FLDisp(self): #Line 14 print self.Fno, Furniture.FRDisp(self) Fixture.FXDisp(self) FL=Flat(101) #Line 15 FL.More(2) FL.FLDisp()

(i) Write the type of the inheritance illustrated in the above.

(ii) Find and write the output of the above code.

(iii) What is the difference between the statements shown in Line 11 and Line 12?

(OR)

Define inheritance. Show brief python example of Single Level, Multiple and Multilevel Inheritance.

CBSECBSE Class XII Board 2019Subjective· 4mImportance★★★★★est

99% · 96/97 Questions

🔒 Locked · start free trial →

You're viewing a preview — the full solution, concept, methods & PYQ mapping are locked.

Start your 14-day free trial to unlock the full solution →

Part (a)Concept understanding — Function Call Handling

Function Call Handling

Think about what happens when you ask a friend for a favour. You stop what you're doing, explain what you need, and then wait while your friend does the work. Once they finish, they come back to you with the result, and you resume whatever you were doing. That simple back-and-forth is the essence of how function calls work in programming.

The Everyday Intuition

Imagine you're cooking a meal. You have a recipe book open. The main recipe says "prepare the sauce" — but it doesn't list every single step for making the sauce right there. Instead, it expects you to know a separate sauce recipe. So you pause the main cooking, go make the sauce, and when it's ready, you return to the main dish and continue. The sauce recipe is like a function: a self-contained set of instructions that does one specific job.

In programming, a function call is exactly this: the main program says "go do this specific task," hands over any necessary information, waits for the task to complete, and then gets back whatever result the function produced.

The Precise Meaning

A function call is the instruction that tells the computer to execute a predefined block of code — the function — and then return control back to the point where the call was made. The function itself is a named, reusable set of instructions that performs a particular operation.

When a function is called, three things happen in sequence:

The current task is paused — the computer remembers exactly where it was in the main program.
Control is transferred to the function, along with any data the function needs to do its job (these are called arguments or parameters).
The function runs its instructions, produces a result (if any), and returns control — along with that result — back to the exact spot where the call was made.

Note

The key idea is temporary suspension. The main program does not end when a function is called; it simply steps aside, lets the function do its work, and then picks up exactly where it left off. This is different from jumping to a completely new program or starting over.

Why It Matters

Function call handling is not a trivial detail — it is the backbone of how programs are organised. Without it, every program would be one long, flat list of instructions, impossible to manage beyond a few dozen lines.

Here is why this concept is so important:

Reusability — You write a function once and call it as many times as needed. The same "calculate tax" function can be called for every customer without rewriting the logic.
Modularity — A program is broken into small, independent pieces. Each function does one thing well. This makes the program easier to understand, test, and fix.
Abstraction — When you call a function, you do not need to know how it works internally. You only need to know what it does and what information to give it. This is like driving a car without understanding the engine.
Readability — A program that uses function calls reads almost like an outline: "process order, calculate discount, send confirmation." Each step is a function name that describes what happens.

Important

The most common mistake beginners make is thinking that a function call "inserts" the function's code into the main program. It does not. The function's code stays in its own place. The call merely transfers control temporarily. This distinction matters because it explains how the same function can be called from many different places without duplicating code.

How the Computer Keeps Track …

Part (b)Concept understanding — Function Call Handling

Function Call Handling

The Everyday Intuition

The Precise Meaning

When a function is called, three things happen in sequence:

The current task is paused — the computer remembers exactly where it was in the main program.
Control is transferred to the function, along with any data the function needs to do its job (these are called arguments or parameters).
The function runs its instructions, produces a result (if any), and returns control — along with that result — back to the exact spot where the call was made.

Note

Why It Matters

Here is why this concept is so important:

Reusability — You write a function once and call it as many times as needed. The same "calculate tax" function can be called for every customer without rewriting the logic.
Modularity — A program is broken into small, independent pieces. Each function does one thing well. This makes the program easier to understand, test, and fix.
Abstraction — When you call a function, you do not need to know how it works internally. You only need to know what it does and what information to give it. This is like driving a car without understanding the engine.
Readability — A program that uses function calls reads almost like an outline: "process order, calculate discount, send confirmation." Each step is a function name that describes what happens.

Important

How the Computer Keeps Track …

Start your 14-day free trial to unlock the full solution →

Part (a)

Multiple Inheritance — Flat is derived from two base classes, Furniture and Fixture.
FL = Flat(101): Fno = 101; since 101 < 100 is False, Q = 20, and both base constructors set self.Qty = 20. FL.More(2) calls both GetMore methods, taking Qty 20 -> 22 -> 24. In FLDisp, print self.Fno, prints 101 with a trailing comma (no line break in Python 2), then Furniture.FRDisp(self) prints self.Qty on the same line giving 101 24, and finally Fixture.FXDisp(self) prints self.Qty again on the next line:

101 24
24
``` …

Start your 14-day free trial to unlock the full solution →

Part (a): the code shows multiple inheritance; tracing the object gives the output 101 24 then 24, and Lines 11/12 call the Furniture and Fixture constructors. Part (b): inheritance reuses a base class, illustrated with single-level, multiple and multilevel examples.

Part (a)

(i) class Flat(Furniture, Fixture) derives from two base classes -> Multiple Inheritance.

(ii) Trace:

FL = Flat(101) -> Fno = 101; since 101 < 100 is False, Q = 20. Furniture.__init__(self, 20) sets self.Qty = 20; Fixture.__init__(self, 20) sets self.Qty = 20 (the same instance attribute).
FL.More(2) -> Furniture.GetMore(self, 2) makes Qty 20 + 2 = 22, then Fixture.GetMore(self, 2) makes Qty 22 + 2 = 24.
FL.FLDisp() runs three statements:
- print self.Fno, prints 101 and, because of the trailing comma, keeps the cursor on the same line.
- Furniture.FRDisp(self) runs print self.Qty, printing 24 on that same line -> 101 24.
- Fixture.FXDisp(self) runs print self.Qty, printing 24 on the next line.

101 24
24

Watch out

Watch the trailing comma in print self.Fno,. In Python 2 it suppresses the newline, so the very next print (inside FRDisp) continues on the same line — that is why 101 and the first 24 appear together as 101 24, not on separate lines. …

Start your 14-day free trial to unlock the full solution →

←Previous questionQ75 — Define a class HOUSE in Python with the following specifications: Inst…→Next questionQ77 — Write a python method/function Swapper(Numbers) to swap the first half…

Q.Answer the questions

Part (a)

🎓Unlock everything free for 14 days

Unlock everything free for 14 days