Revision as of 05:06, 9 November 2023 edit BattyBot (talk \| contribs) Bots 1,957,349 edits →top: Fixed reference date issue(s) (see CS1 maint: date format for details) and AWB general fixes Tag: AWB ← Previous edit		Revision as of 07:57, 3 June 2024 edit undo Citation bot (talk \| contribs) Bots 5,865,649 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 Next edit →
Line 10: To remove a poltergeist, delete the class and insert its functionality in the invoked class, possibly by [[Inheritance (object-oriented programming)\|inheritance]] or as a [[mixin]]. There have been proposed methods in detecting poltergeists in code for refactoring.<ref>{{cite ~~journal~~book \|last1=Al-Rubaye \|first1=Samer Raad Azzawi \|last2=Selcuk \|first2=Yunus Emre \|title=2017 8th IEEE International Conference on Software Engineering and Service Science (ICSESS) \|chapter=An investigation of code cycles and Poltergeist anti-pattern \|date=24–26 November 2017 \|pages=139–140 \|doi=10.1109/ICSESS.2017.8342882 \|isbn=978-1-5386-0497-7 \|chapter-url=https://ieeexplore.ieee.org/document/8342882/authors#authors}}</ref> ==See also==

Poltergeist (computer programming): Difference between revisions