23 reputation
4
bio website
location
age
visits member for 3 years
seen May 22 at 0:25

Jul
2
awarded  Scholar
Jul
2
accepted Hide or Show singleton?
Jul
1
comment Hide or Show singleton?
Ahhh...Jon Skeet. Thanks @JesseC.Slicer!
Jul
1
comment Hide or Show singleton?
Well if both Sun and Microsoft use that design, I guess it's worth considering! I never considered why that might be the case, but your point goes some way to explain the mentality.
Jul
1
awarded  Editor
Jul
1
revised Hide or Show singleton?
added 569 characters in body
Jul
1
comment Hide or Show singleton?
@DocBrown, you sound lie you've been at that point that you speak of. I think that my scenario (3rd comment down on this question) is a good case for using singletons.
Jul
1
comment Hide or Show singleton?
@Telastyn please clarify. I don't understand what you mean. I thought the whole point of a singleton was to have all modules use the same instance of the class, regardless.
Jul
1
awarded  Supporter
Jul
1
comment Hide or Show singleton?
I guess what you're saying is the test is whether the other objects need to work with the instance directly, right?
Jul
1
awarded  Student
Jul
1
comment Hide or Show singleton?
I'll give people the chance to answer too :)
Jul
1
comment Hide or Show singleton?
@delnan I'm reading through the post. Informative so far. @w4rumy I am not a big fan of "never use..." or "never do...". There is a time and place for everything (as long as it's OOP). In my application, I have a log4net/log4j logger. I've created a class called Logger, and had been wondering whether to provide Logger.Error("") or Logger.Instance.Error(...) functionality. The native libraries all use Instance (e.g. AppDomain), but I feel that it's a bit superfluous.
Jul
1
comment Hide or Show singleton?
Nice answer. I don't have enough reputation to vote-up :(
Jul
1
asked Hide or Show singleton?
Jul
15
answered Is it possible to get entry-level jobs and internships without devoting all your time to programming?