Global Objects & Extern

If you #include globals.h in more than one file, it is a bad idea to define variables there. You're also misusing the "static" keyword. When you have a "static" variable that is not in a class or function, it tells the compiler that no other file should be able to use the variable. (See MSDN for more details.) A better way to do it would be to have something like this:

// In globals.hextern Logger gLog;// In somefile.cpp#include "globals.h"void SomeFunction(){ gLog.DoSomething();}

Better yet, have a look at singletons.

If you make something static, it means that it's only available in that translation unit.

If you make it static in a header, it means that each translation unit including that header gets its own copy.

ApochPiQ is mostly right -- you also need to have, in a single source file, the definition of the logger.

// in globals.h:#include <Logger.h>// in Logger.h:class Logger { ... };extern Logger gLog;// in most files.cpp:#include "globals.h"gLog.Log( "hello, world!\n" );// in Logger.cpp:Logger gLog( "Log.html" );

Note that you have to include the declaration of the class Logger to actually be able to use it in the other files.

Good catch. I guess I'm so used to doing that in my own code that I just take it for granted [wink]

Thanks buddys this helps me! all is fixed.
You'r Ratings up! :)