Difference between Encapsulation and Abstraction

by

Encapsulation hides variables or some implementation that may be changed so often in a class to prevent outsiders access it directly. They must access it via getter and setter methods.

Abstraction is used to hide something too, but in a higher degree (class, interface). Clients who use an abstract class (or interface) do not care about what it was, they just need to know what it can do.

More Related Contents:

  1. Simple way to understand Encapsulation and Abstraction
  2. Difference between abstraction and encapsulation?
  3. Why encapsulation is known as Data Hiding? [closed]
  4. What’s the difference between a method and a function?
  5. Interface vs Base class
  6. Inheritance vs. Aggregation [closed]
  7. What is the difference between an abstract method and a virtual method?
  8. What is “loose coupling?” Please provide examples
  9. How abstraction and encapsulation differ?
  10. Do write-only properties have practical applications?
  11. Why “private” methods in the object oriented?
  12. Why encapsulation is an important feature of OOP languages? [closed]
  13. Doctrine2 ORM does not save changes to a DateTime field
  14. What is composition as it relates to object oriented design?
  15. How do you explain OO to new programmers? [closed]
  16. What is polymorphism, what is it for, and how is it used?
  17. Why use getters and setters/accessors?
  18. Prefer composition over inheritance?
  19. What is the exact problem with multiple inheritance?
  20. Why can’t I seem to grasp interfaces?
  21. Functional programming vs Object Oriented programming [closed]
  22. Explanation of the UML arrows
  23. Where do I use delegates? [closed]
  24. Difference Between Cohesion and Coupling
  25. Polymorphism – Define In Just Two Sentences [closed]
  26. Private vs. Public members in practice (how important is encapsulation?) [closed]
  27. Are there any rules for OOP?
  28. Constructors in Go
  29. In SOLID, what is the distinction between SRP and ISP? (Single Responsibility Principle and Interface Segregation Principle)
  30. When to use a Class in VBA?

Leave a Comment