private data members are generally considered good because they provide encapsulation. Providing getters and setters for them breaks that encapsulation, but it’s still better than public data members because there’s only once access point to that data. You’ll notice this during debugging. If it’s private, you know you can only modify the variable inside the … Read more
BridgePattern decouples an abstraction from its implementation. Abstraction and Implementation can vary independently since the concrete class does not directly implement Abstraction ( interface) Implementation never refers Abstraction. Abstraction contains Implementation interface as a member (through composition). Coming back to your question regarding the example code in [journaldev][4] article : Shape is Abstraction Triangle is … Read more
Generally it means that by increasing the level of abstraction one can make the problem easier to understand/resolve. Be careful with your abstractions though, the full quote at least as I heard it is, “You can solve every problem with another level of indirection, except for the problem of too many levels of indirection”.
Abstraction is a process where you show only “relevant” data and “hide” unnecessary details of an object from the user. Consider your mobile phone, you just need to know what buttons are to be pressed to send a message or make a call, What happens when you press a button, how your messages are sent, … Read more
Abstraction in OOP theory consists in retaining only the relevant aspects of a real world object for a specific problem. Thus we talk about abstraction of the reality. It’s a reduction. For example, in the real world we have cats and dogs that are vertebrate animals. Such an animal has properties such as head and … Read more
Encapsulation: hiding data using getters and setters etc. Abstraction: hiding implementation using abstract classes and interfaces etc.
Interfaces are excellent when you want to create something like it: using System; namespace MyInterfaceExample { public interface IMyLogInterface { //I want to have a specific method that I’ll use in MyLogClass void WriteLog(); } public class MyClass : IMyLogInterface { public void WriteLog() { Console.Write(“MyClass was Logged”); } } public class MyOtherClass : IMyLogInterface … Read more
Go to the source! Grady Booch says (in Object Oriented Analysis and Design, page 49, second edition): Abstraction and encapsulation are complementary concepts: abstraction focuses on the observable behavior of an object… encapsulation focuses upon the implementation that gives rise to this behavior… encapsulation is most often achieved through information hiding, which is the process … Read more
Most answers here focus on OOP but encapsulation begins much earlier: Every function is an encapsulation; in pseudocode: point x = { 1, 4 } point y = { 23, 42 } numeric d = distance(x, y) Here, distance encapsulates the calculation of the (Euclidean) distance between two points in a plane: it hides implementation … Read more
Why use getters and setters/accessors?