- Home /
What we can achieve by putting MonoBehaviour inside namespaces?
Hey guys! As everyone, I'm really excited about Unity 4 coming out in some weeks(or days, maybe..?!). I took a look in the release notes and I found out an interesting update(well, I think it is...):
Scripting: MonoBehaviours can now be inside namespaces.
I want to know what we can achieve by putting MonoBehaviour classes inside namespaces. I'm not a big user of namespaces, so I really don't know much about it.
Our classes will not need to directly derive from MonoBehaviour if some namespace which contains a class that derive from MonoBehaviour is being used?
Thanks from now!
Answer by MadDave · Aug 23, 2012 at 01:02 PM
Namespaces help you to organize your project and prevent name clashes (i.e. problems if several classes, variables have the same name.) This may not be important for small projects, but in professional projects with hundreds of thousands of lines of code it becomes vital. More about namespaces: http://en.wikipedia.org/wiki/Namespace_%28computer_science%29
Up till now developers were not able to put MonoBehaviours in namespaces (due to special treatment inside the engine, I suppose). Apparently this has been fixed now.
This can become handy when you use a plugin from the AssetStore that have a class with a name you already used.
Now you will just need (or expect the developer of the plugin) to put all scripts from the plugin into a dedicated namespace.
Your answer
Follow this Question
Related Questions
UnityEngine found but MonoBehaviour or Vector3 not found in MonoDevelop 1 Answer
using UnityEditor outside of Editor folder when compiling build? 4 Answers
Can't use Namespaces with Mono and 1 class 1 namespace file 1 Answer
namespaces and script names 0 Answers
Unity 5.6.0p3 does not recognize class inside namespace 1 Answer