Poltergeist (computer programming): Difference between revisions

Content deleted Content added

Revision as of 07:57, 3 June 2024 edit Citation bot (talk \| contribs) Bots 5,864,045 edits Alter: title, template type. Add: chapter-url, isbn, pages, chapter. Removed or converted URL. \| Use this bot. Report bugs. \| Suggested by Abductive \| Category:Anti-patterns \| #UCB_Category 16/32 ← Previous edit		Latest revision as of 15:23, 24 October 2024 edit undo Belbury (talk \| contribs) Extended confirmed users, Rollbackers 84,430 edits quote template, cn
(One intermediate revision by the same user not shown)
Line 1: {{Short description\|Computer programming object}} In [[computer programming]], a '''poltergeist''' (or '''gypsy wagon''') is a short-lived, typically [[State (computer science)\|stateless]] object used to perform initialization or to invoke methods in another, more permanent class. It is considered an [[anti-pattern]]. The original definition is by Michael Akroyd ~~1996~~at -the 1996 Object World West Conference:{{cn\|date=October 2024}} :"{{blockquote\|As a [[Vardo (Romani wagon)\|gypsy wagon]] or a [[poltergeist]] appears and disappears mysteriously, so does this short lived object. As a consequence the code is more difficult to maintain and there is unnecessary resource waste. The typical cause for this anti-pattern is poor object design." <!-- I think this is a quote -->}} A poltergeist can often be identified by its name; they are often called "manager_", "controller_", "supervisor", "start_process", etc.