Hmm I don't think that will solve the problem.

Suppose I write the GameEngine with that bool;

GameEngine object1;
GameEngine object2;
GameEngine object3;

object1.Initialize();
object2.Initialize();
object3.Initialize();


I can only have 1 GameEngine object but with that code I can write multiple objects.
I'm not sure but I think a 'static bool m_bInitialized'' will help.

As soon this is set to true once, it will always be true in the whole application ( at least if you don't change it to false again ). I'll test in tomorrow.


Yes I'm the only user, but I asked in the question " suppose if the engine is for more users ".

Change that to a static.
class MyClass
{
public:
MyClass() {
assert(!mInitialized);
mInitialized = true;
}
~MyClass() { }

void initialize() {
// do initialization here
}

void shutdown() {
assert(mInitialized);
// do shutdown logic
mInitialized = false;
}

private:
static bool mInitialized;
};


bool MyClass::mInitialized = false;

Now it is not possible to make 2 of this class (threading issues aside).
Add #ifdef _DEBUG for less release-mode clutter.

[quote name='YogurtEmperor' timestamp='1323219520' post='4891292']
Change that to a static.
class MyClass
{
public:
MyClass() {
assert(!mInitialized);
mInitialized = true;
}
~MyClass() { }

void initialize() {
// do initialization here
}

void shutdown() {
assert(mInitialized);
// do shutdown logic
mInitialized = false;
}

private:
static bool mInitialized;
};


bool MyClass::mInitialized = false;

Now it is not possible to make 2 of this class (threading issues aside).
Add #ifdef _DEBUG for less release-mode clutter.