Re: [Dev-C++] Design decision in C++

[<de...@ci...>]

If you want to use any objects within your class that just uses static 
methods you end up having to instantiate them as singletons in a 
non-standard construction method that you then have to document.

Far simpler to design a conventional class that you then use as a 
singleton.

In article <404...@al...>, dou...@al... 
(Doug MacDonald) wrote:

> This is thread is especially interesting to me, as I'm working on a 
> project that uses Singleton for a number of its classes, and I'm not 
> sure it is warranted.  No one has addressed Michael's original 
> question: what are the tradeoffs between using Singleton and just 
> making the class (or all of its members) static?  I'd like to know 
> about others' experiences with Singleton, in case it's advisable to 
> move from Singleton-based classes to static classes in my project.
> 
> Doug