This question was closed Jan 09, 2014 at 10:36 PM by Jessy for the following reason:

Too subjective and argumentative

Question by balauru · Jan 09, 2014 at 11:40 PM · static architecture design-patterns

Is it a good idea to use static classes?

Is it a good idea to use static classes in Unity? And by this i mean a lot of static classes. Like having a lot of classes named "InputManager", "MapManager", etc. to manage stuff. I know this is not a good idea in object oriented programming, but from what i know, Unity is component based, so is it a good idea to use a lot of static functions in a component based architecture, and if not what is a good architecture for a Unity game? I am also using an event system.

I am also using a static class to communicate between scenes, but i don't think this is a bad idea.

Add comment · Show 2

DaveA · Jan 09, 2014 at 11:49 PM 1

Best asked in the Forums

Benproductions1 · Jan 09, 2014 at 11:57 PM 0

The component system is just another system. Unity uses .NET C# and Boo which are both object oriented program$$anonymous$$g languages. The same principles apply no matter what environment they are in, but none the less this should get asked on the forums

Answers Answers and Comments

20 People are following this question.

Is it a good idea to use static classes?

0 Replies

Follow this Question

Related Questions