C++: Bad practice to use friend classes instead of writing getters / setters?

c++ oop design-patterns class-design friend
Jarx picture Jarx · Mar 5, 2011 · Viewed 9k times · Source

I have two classes which in one aspect work together tightly. They both use functionality of each other that should be only used by them and not by any other class.

  • Is it bad practice if I make those two classes friends so they can directly access and manipulate member variables of each other, without using any getter / setter functions?

Answer

CB Bailey picture CB Bailey · Mar 5, 2011

Both getters and setters and friend classes reduce encapsulation and increase coupling. At least friendship restricts the reduced encapsulation to the explicitly specified classes that need the extra access. The fact that the two classes are now tightly coupled need not be a bad thing, they can be considered a single unit of the overall design.

Related questions

Why does C# not provide the C++ style 'friend' keyword?

The C++ friend keyword allows a class A to designate class B as its friend. This allows Class B to access the private/protected members of class A. I've never read anything as to why this was left out of …

Read More
Overload of pure virtual function

I usually use pure virtual functions for those methods that are required by my code to work well. Therefore, I create interfaces and then other users implement their derived classes. The derived classes have only these virtual functions as public …

Read More
How to call a parent class function from derived class function?

How do I call the parent function from a derived class using C++? For example, I have a class called parent, and a class called child which is derived from parent. Within each class there is a print function. In …

Read More