C++ Brain Teasers: Exercise Your Mind/

...

/

Discussion: All Good Things Must Come to an End

Discussion: All Good Things Must Come to an End

Execute the code to understand the output and gain insights into constructors with local state variables.

We'll cover the following...

Run the code

Now, it’s time to execute the code and observe the output.

Press + to interact
#include <iostream>
#include <string>
struct Connection
{
    Connection(const std::string &name) : name_(name)
    {
        std::cout << "Created " << name_ << "\n";
    }
    ~Connection() 
    {
        std::cout << "Destroyed " << name_ << "\n";
    }
    std::string name_;
};
Connection global{"global"};
Connection &get()
{
    static Connection localStatic{"local static"};
    return localStatic;
}
int main()
{
    Connection local{"local"};
    Connection &tmp1 = get();
    Connection &tmp2 = get();
}

A quick recap

In the Hack the Planet! and Going Global puzzles, we learned about the lifetime and initialization differences between a global variable and a local variable:

Press + to interact
int id; // global variable, one instance throughout the whole program
void f() 
{
    int id = 2; // local variable, created anew each time `f` is called
}

In this puzzle, we add two new interesting aspects to the object lifetime:

  • We no longer initialize the variables to a simple constant; there is a constructor with a side effect.

  • We introduce a local variable localStatic with static storage duration.

So, how does the behavior change when we introduce a constructor and a local static variable?

Global variable

Let’s first consider the global variable global. Like the global variable id we saw previously, it has static storage duration, which means only one instance is alive from its initialization until its destruction at the very end of the program.

We previously saw that the global int id; without an initializer was zero-initialized. We also mentioned that a global with an initializer ...