Poltergeist (computer programming): Difference between revisions

Revision as of 19:09, 18 March 2007

Revision as of 19:10, 18 March 2007

Line 1:

{{verify}}

Some may wonder why in the world I have destroyed your beloved article, but they know nothing. Some users fight for law and order in this massive encyclopedia, but I now proclame myslef on the side of mischief and mayhem. Why in the world would I want to support the side of destruction and madness? Good question my friends, good question. Perhaps I merely enjoy playing the villian, or neaby there is some method to my madness.

In [[computer programming]], a '''poltergeist''' (or '''gypsy wagon''') is a short-lived, typically stateless object used to perform initialization or to invoke methods in another, more permanent class. The original definition is by Michael Akroyd 1996 - Object World West Conference:

Nope.

:"As a 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 antipattern 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_", "start_process", etc.

Reason, order, existance, what do these things mean? Where are they going? What is thier purpose? None that I can see. So if I were to bring choas to this world Wikipedia, it would not matter.

Poltergeists should not be confused with long-lived, state-bearing objects of a [[pattern]] such as [[Model-view-controller]], or tier-separating patterns such as [[Business-Delegate]].

SEE YOU SOON!!!

-Q?

To remove a poltergeist, delete the class and insert its functionality in the invoked class.

Poltergeists are examples of an [[anti-pattern]].

[[Category:Anti-patterns]]