Friend Classes and Functions

However, this can be inflexible. There are many cases where we want more granular control.

For example, our class might have some data and methods that are of particular interest to another specific class or function. But we don't want to make them public for everyone - that's too heavy-handed and can eliminate the benefits of encapsulation.

Instead, we can solve these problems by having our class befriend the other class, using the friend keyword.

A class can declare free functions (ie, a function that is not part of another class) as friends using the friend keyword, followed by the function signature. In the following example, MyClass befriends three different functions:

1class MyClass {
2  friend void SomeFunction();
3  friend bool AnotherFunction(int);
4  friend void OneMore(int, float);
5};

More generally, the syntax is

1friend return_type function_name(argument_list);

Any function our class identifies as a friend will have access to everything in our class, including protected and private members.

Here is a complete example, where our class befriends the void LogCalls(MyClass) function, giving it access to the private Calls variable:

1#include <iostream>
2
3// Forward Declarations
4class MyClass;
5void LogCalls(MyClass);
6
7class MyClass {
8  friend void LogCalls(MyClass);
9
10public:
11  void operator()(){ ++Calls; }
12
13private:
14  int Calls{0};
15};
16
17void LogCalls(MyClass Functor){
18  std::cout << "That functor has been called "
19    << Functor.Calls << " times";
20}
21
22int main(){
23  MyClass Functor;
24  Functor();
25  Functor();
26  Functor();
27  LogCalls(Functor);
28}

1That functor has been called 3 times

To help with code organization, C++ also allows us to define friend functions within the class that they are a friend of. It looks like this:

1#include <iostream>
2
3class MyClass {
4public:
5  void operator()(){ ++Calls; }
6
7  friend void LogCalls(MyClass Functor) {
8    std::cout << "That functor has been called "
9      << Functor.Calls << " times";  
10  }
11
12private:
13  int Calls{0};
14};

Whilst the previous example looks like LogCalls() is a member function, the use of the friend keyword in this context is creating a non-member function. This allows LogCalls() to be used like a free function, exactly as we did before:

1#include <iostream>
2
MyClass|Show
3class MyClass {/*...*/};
16
17int main(){
18  MyClass Functor;
19  Functor();
20  Functor();
21  Functor();
22  LogCalls(Functor);
23}

1That functor has been called 3 times

Our class can befriend another class, using the friend class syntax:

1class MyClass {
2  friend class Analytics;
3};

This gives any member of Analytics access to any member of MyClass:

1#include <iostream>
2
3class MyClass {
4  friend class Analytics;
5
6public:
7  void operator()(){ ++Calls; }
8
9private:
10  int Calls{0};
11};
12
13class Analytics {
14public:
15  static void LogCalls(MyClass Functor){
16    std::cout << "That functor has been called "
17      << Functor.Calls << " times";
18  }
19};
20
21int main(){
22  MyClass Functor;
23  Functor();
24  Functor();
25  Functor();
26  Analytics::LogCalls(Functor);
27}

1That functor has been called 3 times

Where we want to befriend a class function, the syntax is similar to what we used to befriend a free function. We have to add the class name and the scope resolution operator to our friend statement:

1// Forward Declaration
2class MyClass;
3
4class Analytics {
5public:
6  static void LogCalls(MyClass Functor);
7};
8
9class MyClass {
10  friend void Analytics::LogCalls(MyClass);
11};

The following code shows a complete example of this. Note, that we've moved the definition of Analytics above the definition of MyClass in this example. We've then also had to move the definition of Analytics::LogCalls below the definition of MyClass.

This is to ensure everything is appropriately defined before it is used. In real programs, this is rarely an issue, as our classes would be in separate header files:

1#include <iostream>
2
3class MyClass;
4
5class Analytics {
6public:
7  static void LogCalls(MyClass Functor);
8};
9
10class MyClass {
11  friend void Analytics::LogCalls(MyClass);
12
13public:
14  void operator()(){ ++Calls; }
15
16private:
17  int Calls{0};
18};
19
20void Analytics::LogCalls(MyClass Functor){
21  std::cout << "That functor has been called "
22    << Functor.Calls << " times";
23}
24
25int main(){
26  MyClass Functor;
27  Functor();
28  Functor();
29  Functor();
30  Analytics::LogCalls(Functor);
31}

1That functor has been called 3 times

We can befriend class and function templates by declaring template parameters in the normal way

1class MyClass {
2  // Befriending a class template
3  template <typename>
4  friend class Analytics;
5
6  // Befriending a function template
7  template <typename T>
8  friend void LogCalls(T);
9};

In this example, every instantiation of the template, including specializations of the template, is befriended.

If we want to befriend just a specific instantiation of a template class or function, we can provide the template parameters within our friend statement. This requires that the templates have already been declared:

1// Forward Declarations
2template <typename T>
3class Analytics;
4
5template <typename T>
6void LogCalls(T);
7
8class MyClass {
9  friend class Analytics<MyClass>; 
10  friend void LogCalls<MyClass>(MyClass); 
11};

A complete, working example using both a class template and a function template is below:

1#include <iostream>
2
3class MyClass {
4  template <typename>
5  friend class Analytics;
6
7  template <typename T>
8  friend void LogCalls(T);
9
10public:
11  void operator()(){ ++Calls; }
12
13private:
14  int Calls{0};
15};
16
17template <typename T>
18class Analytics {
19public:
20  static void LogCalls(T Functor){
21    std::cout << "That functor has been called "
22      << Functor.Calls << " times\n";
23  }
24};
25
26template <typename T>
27void LogCalls(T Functor){
28  std::cout << "That functor has been called "
29    << Functor.Calls << " times";
30}
31
32int main(){
33  MyClass Functor;
34  Functor();
35  Functor();
36  Functor();
37  Analytics<MyClass>::LogCalls(Functor);
38  LogCalls(Functor);
39}

1That functor has been called 3 times
2That functor has been called 3 times

Constructors can have access specifiers, just like any other member function. By making a constructor private, we prevent objects of that class from being created directly by external code.

This might seem strange - what good is a class if we can't create instances of it? The key is that the class itself, or its friends, can still call the private constructor. This gives us fine-grained control over how and when objects are created.

A common pattern is to provide a public static function that calls the private constructor and returns an object. This is known as a Factory Method, and it's useful for situations where object creation is complex or needs to be controlled.

For example, we can use a factory method to validate constructor arguments before creating an object:

1#include <iostream>
2#include <string>
3#include <stdexcept>
4#include <memory>
5
6class User {
7public:
8  static std::unique_ptr<User> Create(
9    const std::string& Name
10  ) {
11    if (Name.length() < 3) {
12      throw std::invalid_argument(
13        "Username is too short"
14      );
15    }
16    // We can access the private constructor from
17    // a static member function
18    return std::unique_ptr<User>(new User(Name));
19  }
20
21  void Greet() const {
22    std::cout << "Hello, " << Name << "!\n";
23  }
24
25private:
26  User(const std::string& Name) : Name(Name) {}
27  std::string Name;
28};
29
30int main() {
31  // This would fail as the constructor is private
32  // User u1("Direct"); 
33
34  try {
35    auto User1{User::Create("Alice")};
36    User1->Greet();
37
38    auto User2{User::Create("Bo")}; 
39    User2->Greet();
40  } catch(const std::exception& e) {
41    std::cerr << "Error: " << e.what();
42  }
43}

1Hello, Alice!
2Error: Username is too short

This pattern can be extended using the friend keyword. Instead of a static member function, we can delegate the responsibility of object creation to a completely separate class.

This is useful when one class's lifecycle is managed by another, such as a GameObjectManager being responsible for creating all GameObject instances in a game.

By making the manager a friend of the object class, only the manager can create new objects, enforcing a clear and safe object management policy.

1#include <iostream>
2#include <string>
3#include <vector>
4#include <memory>
5
6// Forward declaration
7class Worker;
8
9class Manager {
10public:
11  // This manager is responsible for creating workers
12  std::shared_ptr<Worker> HireWorker(
13    const std::string& Name);
14
15  void ListTeam() const;
16
17private:
18  std::vector<std::shared_ptr<Worker>> Team{};
19};
20
21class Worker {
22private:
23  // Only the Manager class can call this constructor
24  Worker(const std::string& Name) : Name{Name} {}
25  std::string Name{};
26
27  friend class Manager;
28};
29
30// Implementation must come after Worker is fully defined
31std::shared_ptr<Worker> Manager::HireWorker(
32  const std::string& Name
33) {
34  // We can call the private constructor because
35  // Manager is a friend
36  auto NewWorker{
37    std::shared_ptr<Worker>{new Worker{Name}}
38  };
39  Team.push_back(NewWorker);
40  return NewWorker;
41}
42
43void Manager::ListTeam() const {
44  std::cout << "Current Team:\n";
45  for(const auto& WorkerInstance : Team) {
46    // Manager can also access private members
47    std::cout << "- " << WorkerInstance->Name << '\n';
48  }
49}
50
51
52int main() {
53  Manager TheManager{};
54  TheManager.HireWorker("Charlie");
55  TheManager.HireWorker("Dana");
56
57  TheManager.ListTeam();
58
59  // The following line would cause an error
60  // due to the constructor being private
61  // Worker RogueWorker{"Rogue"}; 
62}

1Current Team:
2- Charlie
3- Dana

In this example, the Worker class has a private constructor, and it befriends Manager. This ensures that Worker objects can only be created via the Manager::HireWorker() method, giving the Manager class complete control over the creation and lifecycle of its Worker objects.

It's worth noting some properties of the friend keyword:

1. A friend Declaration can Appear Anywhere in the Class

It doesn't matter where the friend statement appears within our class. It can come at the start, the end, or anywhere in between - the effect is the same.

2. A friend Declaration is not Subject to Access Specifiers

It doesn't matter if a friend statement appears in a public, protected, or private part of the class - the effect is the same

3. A friend Declaration is not Mutual

If A declares B a friend, that does not give A additional access to B.

For that, B needs to explicitly declare A a friend too.

4. A friend Declaration is not Transitive

If A declares B a friend, and B declares C a friend, that does not give C additional access to A.

For that, A needs to explicitly declare C a friend.

5. A friend Declaration is not Inherited

If Child inherits from Parent, and Parent declares SomeClass a friend, that does not grant SomeClass access to Child.

For that, Child needs to declare SomeClass a friend explicitly.

In this lesson, we explored the concept of friend functions and classes, which allow for controlled access to a class's private and protected members.

Main Points Learned

• The friend keyword grants specific external functions and classes access to a class's private and protected members.
• A class can declare a free function a friend.
• Friend functions can be defined within the class that befriends them, and then called like a free function using argument-dependent lookup (ADL)
• A class can declare another class as a friend, allowing all member functions of the friend class access to its private and protected members.
• It's possible to declare specific member functions of another class as friends.
• Friend declarations can also apply to template classes and functions, with the ability to specify all or particular instantiations.
• Friend relationships are not mutual, transitive, or inherited, highlighting the need for explicit declarations to maintain secure and intended access levels.
• The placement of a friend declaration within a class does not affect its access, and it is not affected by access specifiers.