Skip to main content

Home/ Coders/ Group items matching "singleton-pattern" in title, tags, annotations or url

Group items matching
in title, tags, annotations or url

Sort By: Relevance | Date Filter: All | Bookmarks | Topics Simple Middle
1More

Why Singletons Are Controversial - google-singleton-detector - A brief explanation of t... - 0 views

code.google.com/...WhySingletonsAreControversial design patterns singleton
shared by Fabien Cadet on 17 Mar 09 - Cached
  • Fabien Cadet on 17 Mar 09
     
    * Introduce a global state in the program, hide the dependencies. * Test-driven development: classes become tightly coupled with the singleton. Need to test the singleton along with the class to be tested initially.
2More

Singleton pattern - Wikipedia, the free encyclopedia - 0 views

en.wikipedia.org/...Singleton_pattern singleton-pattern programming
shared by Tarik Guney on 03 Nov 09 - Cached
  • the singleton pattern is a design pattern that is used to restrict instantiation of a class to one object.
  • Tarik Guney on 03 Nov 09
     
    In software engineering, the singleton pattern is a design pattern that is used to restrict instantiation of a class to one object. This is useful when exactly one object is needed to coordinate actions across the system. The concept is sometimes generalized to systems that operate more efficiently when only one object exists, or that restrict the instantiation to a certain number of objects (say, five). Some consider it an anti-pattern, judging that it is overused, introduces unnecessary limitations in situations where a sole instance of a class is not actually required, and introduces global state into an application.
7More

Use your singletons wisely - 0 views

www.ibm.com/...co-single.html design patterns singleton
shared by Fabien Cadet on 17 Mar 09 - Cached
  • I know where you live anti-pattern
  • Liskov Substitution Principle
  • the easier it is to test a class, the more likely a developer will test it.
  • ...3 more annotations...
  • Don't worry: the code will always tell you what to do. Just listen.
  • The key points here are that a class is only a singleton if all applications treat it exactly the same and if its clients can use the class without an application context.
  • "[c]ode wants to be simple."
  • Fabien Cadet on 17 Mar 09
     
    "singletons are unnecessarily difficult to test and may make strong assumptions about the applications that will use them [...] I know where you live anti-pattern [...] Liskov Substitution Principle". "To decide whether a class is truly a singleton: * Will every application use this class exactly the same way? (exactly is the key word) * Will every application ever need only one instance of this class? (ever and one are the key words) * Should the clients of this class be unaware of the application they are part of?"
1 - 3 of 3
Showing 20▼ items per page