[Silver]

Howdy,

We all know that using global variables eliminates all abstraction and basically means a bad design.

int APIENTRY WinMain(HINSTANCE hInstance,
                     HINSTANCE hPrevInstance,
                     LPTSTR    lpCmdLine,
                     int       nCmdShow)
{
	CGame::Instance()->Init(hInstance);  // Initialize the subsystems
 
 
	while (CGame::Instance()->getGameWnd()->HandleMessages())
	{
		CGame::Instance()->Run();
	}
 
 
	CGame::Instance()->Shutdown();
 
	return 0;
}

This is the main.cpp of the project I'm currently working on, with the error handling removed. Basically, my CGame is a class that is accessible to everyone from everywhere - ****y, but flexible. It is also the top container of all data in my application. It contains pointers to all different subsystems like the graphics subsystem, the game logic subsystem, the sound subsystem, the window subsystem etc. Through CGame::Instance()->get***(), each class can aquire a pointer to the subsystem it wants and work with it. That way, all objects on my world can 'see' each other and interact with each other the way they are programmed to. And I really do not see a possible 'abstracted' alternative - maybe someone can point me out!

Here is an example situation in my project. The CRabbit class implements the functionality of a bunny and is inherited from ICreature. Each ICreature must implement a Draw() routine. Since the graphical output in my app is quite complicated, it's wrapped with the CGraphics class. So my shrinked code for CBunny::Draw() looks as follows:

void CBunny::Draw()
{
	CGame::Instance()->getGraphics()->DrawMesh(this->mesh);
}

Which really does look natural to me. I have only one game, only one graphical subsystem, only one memory manager etc running during the entire application lifetime. So I really (and I mean really, please) want to see a bulletproof reply of a better alternative for the design, provided with arguments and all. Anyone?

[Agregat]

Зайцу не надо знать о том, что такое игра. Более того, он не должен знать, как и зачем его рисуют. Он должен экспортировать mesh, а дальше RenderManager должен заниматься тем, что по очереди рисовать все объекты. Более того, только рендерер может знать что рисовать, а что нет - так как только у него есть правильный З-порядок. А заяц, о своем порядке знать не долже. Ну и т.д.

[Silver]

So am I getting you right that a better design would be splitting all entities existing within the scope of the task into 'Data Containers' (CMesh, CHuman, CRabbit...) and 'Action Performers' (CRenderer, CWalker, CDLLManager, CLogger...). But then again (if that's what you mean), aren't all 'Action Performers' singletons by their nature?

Also another question, if a bunny lives in a specific world, I assume he knows how to live in it. I assume he knows how to handle other animals on the same world, how to eat the grass growing on that world, how to draw itself and how to have sex with any other creature, that's at least how it seems natural to me. I want to think of a bunny as of something more than just a bunch of parameters, something that makes use of the world it lives in for the survival of its own, the way its programmed to use it. Isn't that how the real world is constructed? I am too unexperienced and the opinions I express could seem too immature, though. Why not give all the objects all the knowledge about the entire world (like in the real life) and limit their ability to modify it merely by the implementation of the specific creature (like in real life)?

If the universe logics solely exists within some CUniverseLogic(), we can't hope to expand it later by adding revolutionary creatures to the world - can we? We'll have to modify the universe logics core. Go deeper with this, please. Also, if anyone could advise some good reading, that'd be fantastic. Thanks a lot.

[Agregat]

Заяц не есть контейнер - заяц есть заяц. Так как у тебя может быть миллион зайцев.
Заяц должен уметь Есть, Срать и Трахаться. У него должны быть соответствующие методы. Он должен уметь есть траву и не есть мясо. Но он не должен уметь себя рисовать. Так как заяц сквозь сеточные глаза пчелы и в моих глазах выглят по разному. Рендерер должен определять как выглятит тот или иной заяц в разных контекстах, а вот форма у зайца есть - поэтому меш он должен экспортировать.

[Griffon2-7]

Originally Posted by Agregat

Так как заяц сквозь сеточные глаза пчелы и в моих глазах выглят по разному.

Держите себя в руках, Виктор! Держите себя в руках!

[Agregat]

Держу. Стараюсь, по крайней мере!