<h1 id="the-liskov-substitution-principle"><a aria-hidden="true" class="anchor-heading icon-link" href="#the-liskov-substitution-principle"></a>The Liskov Substitution Principle</h1>
<blockquote>
“Functions that use pointers or references to base classes must be able to use objects of derived classes without knowing it”
</blockquote>
Alternatively, this can be expressed as “Derived classes must be substitutable for their base classes”
<blockquote>
For example, the sub-class “Platypus”, of the base class “Mammals”, would have the exception that these mammals lay eggs. The LSP, tell us that it would create a function called “give_birth”, this function will have different behavior for the sub-class Platypus and the sub-class Dog. Therefore, we should have had a more abstract base class than Mammals that accommodate this.
If this sounds very confusing, do not worry, the application of this latter aspect of the LSP is rarely fully implemented, and it rarely leaves the theoretical textbooks.
</blockquote>
<hr>
<ul>
<li>Reference:
<ul>
<li><a href="/DevLog/notes/9knz69r6nooffoynnm56e9h">SOLID Coding in Python</a></li>
</ul>
</li>
</ul>
<hr>
Backlinks
<ul>
<li><a href="/DevLog/notes/9knz69r6nooffoynnm56e9h">Solid Coding in Python (DevLog)</a></li>
</ul>

The Liskov Substitution Principle


The hyperfixated rabbit hole diving knowledge base that is my brain looking at technology.
