Should I use manager classes? (Singletons)

[GreatJake]

Recently I read this blog thingy...
http://gameprogrammingpatterns.com/singleton.html

It basically says you should only use singletons on very rare occasions..

In the game I'm currently creating I have a bunch of singletons, for example i have a Box2DManager, CameraManager, InterfaceManager, MouseManager, KeyboardManager, MapManager, ProjectileManager, ResourceManager, TimeManager. Am i being too liberal with these singletons? Should i be passing these as parameters?

For example i can just do this.

Code: Select all

#include "MapManager"
#include "ResourceManager"

MapMgr->getMap()->addEntity(ResourceMgr->createEntity("box");

And boom instant box in my game. Whats so wrong with getting everything you want when you want it with a simple #include??

[LuisR14]

i think it depends on the implementation of those classes (i'm not very sure), and like dam, that's some lot of managers xD

[chili]

Yeah, it's not really a good design paradigm. I could explain reasons why, but that article you linked does a really good job and I'd just be repeating what was said there, only not as well.


Still, I say if it works for you personally, then who cares? I think as you create more complicated systems, you'll naturally find out why globals in general aren't a good idea. And if they never are a problem for you, then more power to you. If it feels good do it. Even if you shouldn't. Don't let people mess you around.

[jkhippie]

It seems to me that globals and Singletons are a bigger problem in a team environment. If you declare a bunch - o - shit, just keep track of it and it's fine. Right? -ish?