Circular class dependency
- by shad0w
Is it bad design to have 2 classes which need each other?
I'm writing a small game in which I have a GameEngine class which has got a few GameState objects. To access several rendering methods, these GameState objects also need to know the GameEngine class - so it's a circular dependency.
Would you call this bad design? I am just asking, because I am not quite sure and at this time I am still able to refactor these things.