Why not use instanceof operator in OOP design?

by

instanceof simply breaks the Open/Close principle. and/or Liskov substitution principle

If we are not enough abstract because of instanceof usage, each time a new subclass makes an entrance, the main code gathering the logic of the application might be updated.
This is clearly not what we want, since it could potentially break the existing code and reduce its reusability.

Therefore, a good usage of polymorphism should be preferred over the basic use of conditional.

More Related Contents:

  1. Interface vs Abstract Class (general OO)
  2. Interface vs Base class
  3. What is the difference between association, aggregation and composition?
  4. What is Inversion of Control?
  5. When to use an interface instead of an abstract class and vice versa?
  6. What does “program to interfaces, not implementations” mean?
  7. C++ equivalent of java’s instanceof
  8. Method chaining – why is it a good practice, or not?
  9. What is the difference between an Instance and an Object?
  10. Does functional programming replace GoF design patterns?
  11. What is the use of making constructor private in a class?
  12. What is the definition of “interface” in object oriented programming
  13. Is returning null bad design? [closed]
  14. Why don’t associated types for protocols use generic type syntax in Swift?
  15. What is the scope of the Single Responsibility Principle? [closed]
  16. How much work should be done in a constructor?
  17. When to use mixins and when to use interfaces in Dart?
  18. When should I use static methods in a class and what are the benefits?
  19. What is an example of the Single Responsibility Principle? [closed]
  20. Mediator Vs Observer Object-Oriented Design Patterns
  21. Doctrine2 ORM does not save changes to a DateTime field
  22. Can’t seem to understand SOLID principles and design patterns [closed]
  23. Is it bad practice for a class to have only static fields and methods?
  24. How to create a “single dispatch, object-oriented Class” in julia that behaves like a standard Java Class with public / private fields and methods
  25. Constructors in Go
  26. Difference between Encapsulation and Abstraction
  27. Coupling, Cohesion and the Law of Demeter
  28. When to use delegation instead of inheritance? [closed]
  29. How do you explain OO to new programmers? [closed]
  30. Aspect Oriented Programming vs. Object-Oriented Programming

Leave a Comment