Why Ogre::Singleton<T> throws runtime error instead of compile time one
Posted: Fri Jun 14, 2019 5:24 pm
Hi all,
I would like to know why the Ogre::Singleton<T> class is written in a way that it throws a runtime error instead of use the standard singleton design pattern?
I'm trying to write a tutorial about the Terrain and I need to understand why the Ogre::TerrainGlobalOptions class is written in this way to explain it correctly.
I would like to know why the Ogre::Singleton<T> class is written in a way that it throws a runtime error instead of use the standard singleton design pattern?
I'm trying to write a tutorial about the Terrain and I need to understand why the Ogre::TerrainGlobalOptions class is written in this way to explain it correctly.