Poltergeist (computer programming): Difference between revisions

Revision as of 17:08, 4 December 2018

Revision as of 22:06, 6 June 2019

Line 6:

A poltergeist can often be identified by its name; they are often called "manager_", "controller_", "supervisor", "start_process", etc.

Sometimes, poltergeist classes are created because the programmer anticipated the need for a more complex architecture. For example, a poltergeist arises if the same method acts as both the ''client'' and ''invoker'' in a [[Commandcommand pattern]], and the programmer anticipates separating the two phases. However, this more complex architecture may actually never materialize.

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

To remove a poltergeist, delete the class and insert its functionality in the invoked class, possibly by [[Inheritance (computer science)|inheritance]] or as a [[mixin]].