Use of static variables and functions in global scope

Question

Is there a use for flagging a variable as static, when it lies in the global scope of a .cpp file, not in a function?

Can you use the static keyword for

Answer 1

Yes, if you want to declare file-scope variable, then static keyword is necessary. static variables declared in one translation unit cannot be referred to from another translation unit.

---

By the way, use of static keyword is deprecated in C++03.

The section $7.3.1.1/2 from the C++ Standard (2003) reads,

The use of the static keyword is deprecated when declaring objects in a namespace scope; the unnamed-namespace provides a superior alternative.

C++ prefers unnamed namespace over static keyword. See this topic:

Superiority of unnamed namespace over static?

Answer 2

In this case, keyword static means the function or variable can only be used by code in the same cpp file. The associated symbol will not be exported and won't be usable by other modules.

This is good practice to avoid name clashing in big software when you know your global functions or variables are not needed in other modules.

Answer 3

Taking as an example -

// At global scope
int globalVar; // Equivalent to static int globalVar;
               // They share the same scope
               // Static variables are guaranteed to be initialized to zero even though
               //    you don't explicitly initialize them.


// At function/local scope

void foo()
{
    static int staticVar ;  // staticVar retains it's value during various function
                            // function calls to foo();                   
}

They both cease to exist only when the program terminates/exits.