SOLID Class Design: The Liskov Substitution Principle — Tom Dalling
This is part three of a five part series about SOLID class design principles by Robert C. Martin. The SOLID principles focus on achieving code that is maintainable, robust, and reusable. In this post, I will discuss the Liskov Substitution Principle.
This is part three of a five part series about SOLID class design principles by Robert C. Martin . The SOLID principles focus on achieving code that is maintainable, robust, and reusable. In this post, I will discuss the Liskov Substitution Principle. The Liskov Substitution Principle (LSP) : functions that use pointers to base classes must be able to use objects of derived classes without knowing it . When first learning about object oriented programming, inheritance is usually described as an “is a” relationship. If a penguin “is a” bird, then the Penguin class should inherit from the Bird c
related reading
- SOLID Design Principles Explained- Stackifystackify.com
- SOLID Design Principles Explained: Building Better Software Architecture | DigitalOceandigitalocean.com
- SOLID Class Design: The Open Closed Principle — Tom Dallingtomdalling.com
- Liskov substitution principle - Wikipediaen.wikipedia.org
- LEAP 71 | PicoGK.org Blogpicogk.org
- The Law of Leaky Abstractions – Joel on Softwarejoelonsoftware.com
- Rise of Worse Is Betterdreamsongs.com
- Design Patternsrefactoring.guru
- Object-Oriented Design and Data Structuresandrewcmyers.github.io
- How to write the perfect functionyoutube.com
- Service Locator violates encapsulationblog.ploeh.dk
- Design Patternsgrantslatton.com