Whenever someone says to you, "You should always make data private," stop right there — it's an "always" or "never" rule, and those rules are what I call one-size-fits-all rules. The real world isn't that simple.Here's the way I say it: if I expect derived classes, I should ask this question: who will create them? If the people who will create them will be outside your team, or if there are a huge number of derived classes, then and only then is it worth creating a protected interface and using private data. If I expect the derived classes to be created by my own team and to be reasonable in number, it's just not worth the trouble: use protected data. And hold your head up, don't be ashamed: it's the right thing to do!The benefit of protected access functions is that you won't break your derived classes as often as you would if your data was protected. Put it this way: if you believe your users will be outside your team, you should do a lot more than just provide get/set methods for your private data. You should actually create another interface. You have a public interface for one set of users, and a protected interface for another set of users. But they both need an interface that is carefully designed — designed for stability, usability, performance, etc. And at the end of the day, the real benefit of privatizing your data (including providing an interface that is coherent and, as much as possible, opaque) is to avoid breaking your derived classes when you change that data structure.But if your own team is creating the derived classes, and there are a reasonably small number of them, it's simply not worth the effort: use protected data. Some purists (translation: people who've never stepped foot in the real world, people who've spent their entire lives in an ivory tower, people who don't understand words like "customer" or "schedule" or "deadline" or "ROI") think that everything ought to be reusable and everything ought to have a clean, easy to use interface. Those kinds of people are dangerous: they often make your project late, since they make everything equally important. They're basically saying, "We have 100 tasks, and I have carefully prioritized them: they are all priority 1." They make the notion of priority meaningless.You simply will not have enough time to make life easy for everyone, so the very best you can do is make life easy for a subset of the world. Prioritize. Select the people that matter most and spend time making stable interfaces for them. You may not like this, but everyone is not created equal; some people actually do matter more than others. We have a word for those important people. We call them "customers."
C++
Topic: Inheritance
I've been told to never use protected data, and instead to always use private data with protected access functions. Is that a good rule?
Browse random answers:
Explain the ISA and HASA class relationships. How would you implement each in a class design?
Does c++ support multilevel and multiple inheritance?
What is RTTI?
What is the difference between composition and inheritance?
What is an accessor?
what is the use of volatile keyword? Give me one example?
Why Call by reference technique is used in case of Copy constructor & not call by value?
Is there any way to write a class such that no class can be inherited from it. Please include code
What do you mean by inheritance?
What does inheritance means in C++? What are the different forms of inheritance? Give an example for each.
How to create object for singleton class?
it possible to inherit the private member in drived class?
Can you prevent your class from being inherited and becoming a base class for some other classes?
what are the advantages and disadvantages of inheritance?
What is the difference between superclass and subclass?
Whether there will be a default constructor provided by the compiler in above case ?class A(){};int main(){A a;}
When should you use multiple inheritance?
What is a modifier?
What is a mutable member?
If a base class has a bunch of overloaded constructors, and an inherited class has another bunch of overloaded constructors, can you enforce a call from an inherited constructor to an arbitrary base constructor?
Can you allow class to be inherited, but prevent the method from being over-ridden?
how to select access modifier & what's need of access modifier?
Can you inherit multiple interfaces?
how many types of Inheritence ?
explain the real word example of multilevel inheritance?
Virtual constructor: Constructors cannot be virtual. Declaring a constructor as a virtual function is a syntax error. Does c++ support multilevel and multiple inheritance?
When would I use inheritance?
How do you express inheritance in C++?
Is it OK to convert a pointer from a derived class to its base class?
What's the difference between public, private, and protected?
Why can't my derived class access private things from my base class?
How can I protect derived classes from breaking when I change the internal parts of the base class?
I've been told to never use protected data, and instead to always use private data with protected access functions. Is that a good rule?
What is inherited from the base class?
Explain about Inheritance between classes ?
Explain about Base & Derived Classes ?
Explain about the Access Control and Inheritance ?
How many Type of Inheritance ?
What are the FORMS OF INHERITANCE ?
Explain about execution of base class constructor ?
What are the Overriding of method(function) in inheritance ?
Explain about Virtual Base Class ?
Why java does not support Multiple Inheritance?
What are Encapsulation, Inheritance and Polymorphism?
What is the object-oriented design,inheritance and dynamic polymorphism in c++?
When should you use multiple inheritance?
What is public, protected, private in C++?
Should I hide member functions that were public in my base class?
Converting Derived* → Base* works OK; why doesn't Derived** → Base** work?
What would be printed out – and in what order? execution order of the constructor and destructor in inheritance.
Inheritance syntax
Explain about Inheritance Overview ?
Explain about Key Properties of C++ Inheritance
