Comments on: The Singleton http://www.wazooinc.com/2008/01/31/the-singleton/ Having fun in game development! Fri, 25 Jul 2008 08:16:52 +0000 http://wordpress.org/?v=2.6 By: wazoo http://www.wazooinc.com/2008/01/31/the-singleton/#comment-1205 wazoo Thu, 05 Jun 2008 14:59:17 +0000 http://www.wazooinc.com/2008/01/31/the-singleton/#comment-1205 Thanks for that suggestion Alejandro and glad you like the site! That might be a better way to do this...I know that I don't like launching a game only to see a nasty assertion error dialog pop out at me. My only reasoning behind doing the assert approach is that you could somehow (in the future) use this as a way to trap the problem and create a more helpful way to diagnose / troubleshoot the error. For example, when you see those stack error dialogs come up in World of Warcraft. It gives you the option of submitting the problem / register output to Blizzard for aiding them. Thanks for that suggestion Alejandro and glad you like the site!

That might be a better way to do this…I know that I don’t like launching a game only to see a nasty assertion error dialog pop out at me.

My only reasoning behind doing the assert approach is that you could somehow (in the future) use this as a way to trap the problem and create a more helpful way to diagnose / troubleshoot the error.

For example, when you see those stack error dialogs come up in World of Warcraft. It gives you the option of submitting the problem / register output to Blizzard for aiding them.

]]> By: Alejandro Segovia http://www.wazooinc.com/2008/01/31/the-singleton/#comment-1183 Alejandro Segovia Wed, 28 May 2008 14:46:20 +0000 http://www.wazooinc.com/2008/01/31/the-singleton/#comment-1183 Instead of using asserts to make sure no one calls the constructor more than once, you could make the singleton's constructor protected and provide an static getInstance() method which creates or returns the singleton object as needed. The main advantage of using this approach instead of using assertions is that attempts to create the singleton object will be catched by the compiler, whereas using assertions will probably abort the application if the programmer wasn't careful. Great site, btw! Cheers, Alejandro.- Instead of using asserts to make sure no one calls the constructor more than once, you could make the singleton’s constructor protected and provide an static getInstance() method which creates or returns the singleton object as needed.

The main advantage of using this approach instead of using assertions is that attempts to create the singleton object will be catched by the compiler, whereas using assertions will probably abort the application if the programmer wasn’t careful.

Great site, btw!

Cheers,
Alejandro.-

]]>