Question

Could any body offer me any reason about that?

If we do it like that, what’s the outcome? Compile error?

Answer 1

The problem is that static initialization isn’t just initialization, it is also definition. Take for example:

hacks.h :

class Foo
{
public:
    static std::string bar_;
};

std::string Foo::bar_ = "Hello";

std::string GimmeFoo();

main.cpp :

#include <string>
#include <sstream>
#include <iostream>

#include "hacks.h"

using std::string;
using std::ostringstream;
using std::cout;

int main()
{
    
    string s = GimmeFoo();
    return 0;
}

foo.cpp :

#include <string>
#include <sstream>
#include <iostream>

#include "hacks.h"

using std::string;
using std::ostringstream;
using std::cout;

string GimmeFoo()
{
    Foo foo;
    foo;
    string s = foo.bar_;

    return s;
}

In this case, you can’t initialize Foo::bar_ in the header because it will be allocated in every file that #includes hacks.h. So there will be 2 instances of Foo.bar_ in memory – one in main.cpp, and one in foo.cpp.

The solution is to allocate & initialize in just one place:

foo.cpp :

...
std::string Foo::bar_ = "Hello";
...