Local static variable not unique between dylib, Xcode 4.4.1 bug?

Question

I am wondering if this is a Xcode bug or it is the way the c++ standart is.
I would expect to  see 1 in the console but i see 0.
Anybody know why? Here is the code
In one dylib I have
// Header file
class Foo {
   int i_ = 0;
   Foo(const Foo&) = delete;
   Foo& operator= (Foo) = delete;
   Foo()
public:
   void inc()
      ++i_;
   int geti()
      return i_;
   static Foo& get()
      static Foo instance_;
      return instance_;
   Foo( Foo&&) = default;
   Foo& operator= (Foo&&) = default;
int initialize()
   Foo::get().inc();
   return 10;
class Bar
   static int b_;
// cpp file
#include "ClassLocalStatic.h"
int Bar::b_ = initialize();
and in my application project i have
// main.cpp
#include <iostream>
#include "ClassLocalstatic.h"
int main(int argc, const char * argv[])
   std::cout << Foo::get().geti();
   return 0;
Thanks

Answer 1

thanks for your answer, You are right there is 2 foo singleton at different memory addresses.
I didn't think about when the dylib was loaded. I can't even tell when it is loaded. But I know if i but breaks point I break in the initialize function before breaking in main, but that might be because of this actual setup. So when does a dylib will be loaded? At the first call a program sees that need the dylib?
Here I'explain why it is done this way. My Singleton is a UnitTestRegistry, the Bar class is a UnitTest class and the static variable b_ is a class containing metadata info on the unit test.
I have a macro to define the unit test it is called Make_UnitTest()
So in a cpp I do
Make_UnitTest(MyTest)
     // Test Stuff
The macro will get expanded to
class MyTest_UnitTest: public UnitTestBase
     static UniTestMetaData b_;
     virtual void executeTest();
int MyTest_UnitTest::b_ = initializeAndRegisterUnitTest("MyTest_UnitTest", factoryFunction);
MyTest_UnitTest::executeTest()
// Test Stuff
And in the function initializeAndRegisterUnitTest I call the getInstance of the unit test  registry. This way my unit test are registred at loading time of the program/dll. If you know a better way to automatically register (i know it cuold be manual but i find it too cumbersome), but it wont fix the problem which is that I have two intance of my singleton because the function is inline in a header.
Well this behavior is surprising to me, I didn't know it would do this. But hey it is good to learn right!
Just to make it clear there is no real global!! The singleton is like a global but it is not completly one and the b_ is certainly not global it is a class static memeber...