sajty/ember — comment on commit 73e5736005e157f4c9ce6102d3a923b03480cf68
File:  line 0
By erikhjortsberg:

No, what I meant was that there's probably some older code which don't always follow these design guidelines.
In general I always try to pass instances through references when they are guaranteed to not be null and shouldn't be owned by the called instance.
For these changes I can agree that there's no reason to keep mRoot as a field except for in OgreSetup, as it's part of Ogre and Ogre expect it to be used through the getSingleton methods. But I do want it to be held as a field in OgreSetup, just for clarity's sake.