Possible Duplicate:
Why choose a static class over a singleton implementation?
Static methods vs singletons.
Could it be determined choice here?
What are conditions in which one of these approaches is definetely more suitable then other?
Asked
Active
Viewed 1,085 times
4
-
are you talking about static singleton patter vs singleton patters ? – Pranay Rana Jun 17 '11 at 09:47
-
I'm talking about utility class with static methods vs singleton with methods. – Mike Jun 17 '11 at 09:48
-
1see also: http://stackoverflow.com/search?q=static+singleton+[c%23] – M4N Jun 17 '11 at 09:48
-
you have more than ten questions without an accepted answer. ;) – Peter Lawrey Jun 17 '11 at 10:32
-
I would use an `enum` with one instance as singleton if you need to implement an interface. Otherwise, I would use an `enum` with no instances and static methods as a Utility class. – Peter Lawrey Jun 17 '11 at 10:34
2 Answers
3
Static methods follow the "low coupling and high coherence"-rule more than singletons do. (As long as their implementations don't rely on static member variables.)
StackedCrooked
- 33,620
- 41
- 145
- 274
2
If the static methods solve the same problem as the singleton, then why complicate and write a singleton?
Otherwise, why choose something that solves the wrong problem?
R. Martinho Fernandes
- 219,040
- 71
- 423
- 503