devxlogo

Prefer Private Data Members to Protected Ones

Prefer Private Data Members to Protected Ones

Data members of a class are usually a part of its implementation rather than its interface. They may be replaced when the internal implementation of the class is to be changed, and hence, they should be hidden from other classes. If derived classes need to access these data members, they should use accessor methods (“getters”) rather than directly access data members of another object. As a result, no modification will be required for derived classes when a change is made in the base class:

 class Date { private:int d,m,y //how a date is represented is an implementation detailpublic:int Day() const {return d; } };class DateTime : public Date {int h,m,s};

Now let’s assume that class Date is used mostly on display devices, so it has to supply some method of converting its d,m,y integers into a displayable string. In order to enhance performance, a design modification is made: instead of the three integers, a single string will now hold the date representation. Had class DateTime relied on the internal implementation of Date, it would have had to be modified as well. But since it can access Date’s data members only through access methods, all that is required is a small change in Date::Day() method. Please note that accessor methods are inlined anyway, so their use should not incur any overhead.

See also  Professionalism Starts in Your Inbox: Keys to Presenting Your Best Self in Email
devxblackblue

About Our Editorial Process

At DevX, we’re dedicated to tech entrepreneurship. Our team closely follows industry shifts, new products, AI breakthroughs, technology trends, and funding announcements. Articles undergo thorough editing to ensure accuracy and clarity, reflecting DevX’s style and supporting entrepreneurs in the tech sphere.

See our full editorial policy.

About Our Journalist