Content deleted Content added
m Reverted edits by 213.37.211.130 (talk) to last version by Ripchip Bot |
Ordered listing alphabetically |
||
Line 5:
* [[Chain of responsibility pattern]]: Command objects are handled or passed on to other objects by logic-containing processing objects
* [[Command pattern]]: Command objects encapsulate an action and its parameters
* "Externalize the Stack": Turn a recursive function into an iterative one that uses a stack.<ref>
| url = http://c2.com/
| title = Externalize The Stack
| date = 2010-01-19
| publisher = c2.com
| archiveurl = http://c2.com/cgi/wiki?ExternalizeTheStack
| archivedate= 2010-01-19
| accessdate = 2012-05-21
}}</ref>
* [[Hierarchical visitor pattern]]: Provide a way to visit every node in a hierarchical [[data structure]] such as a tree.▼
* [[Interpreter pattern]]: Implement a specialized computer language to rapidly solve a specific set of problems
* [[Iterator pattern]]: Iterators are used to access the elements of an aggregate object sequentially without exposing its underlying representation
Line 11 ⟶ 20:
* [[Memento pattern]]: Provides the ability to restore an object to its previous state (rollback)
* [[Null Object pattern]]: designed to act as a default value of an object
* [[Observer pattern]]: aka Publish/Subscribe or Event Listener. Objects register to observe an event
** Weak reference pattern: De-couple an observer from an observable.<ref>
| author = Ashod Nakashian
* [[Protocol stack]]: Communications are handled by multiple layers, which form an encapsulation hierarchy.<ref>http://c2.com/cgi/wiki?ProtocolStack</ref>▼
| authorlink = http://c2.com/cgi/wiki?AshodNakashian
| url = http://c2.com/
| title = Weak Reference Pattern
| date = 2004-04-11
| publisher = c2.com
| archiveurl = http://c2.com/cgi/wiki?WeakReferencePattern
| archivedate= 2004-04-11
| accessdate = 2012-05-21
}}</ref>
▲* [[Protocol stack]]: Communications are handled by multiple layers, which form an encapsulation hierarchy.<ref>
| url = http://c2.com/
| title = Protocol Stack
| date = 2006-09-05
| publisher = c2.com
| archiveurl = http://c2.com/cgi/wiki?ProtocolStack
| archivedate= 2006-09-05
| accessdate = 2012-05-21
}}</ref>
* [[Scheduled-task pattern]]: A task is scheduled to be performed at a particular interval or clock time (used in [[real-time computing]])▼
* [[Single-serving visitor pattern]]: Optimise the implementation of a visitor that is allocated, used only once, and then deleted▼
* [[Specification pattern]]: Recombinable Business logic in a boolean fashion▼
* [[State pattern]]: A clean way for an object to partially change its type at runtime
* [[Strategy pattern]]: Algorithms can be selected on the fly
▲* [[Specification pattern]]: Recombinable Business logic in a boolean fashion
* [[Template method pattern]]: Describes the [[program skeleton]] of a program
* [[Visitor pattern]]: A way to separate an algorithm from an object
▲* [[Single-serving visitor pattern]]: Optimise the implementation of a visitor that is allocated, used only once, and then deleted
==References==▼
▲* [[Hierarchical visitor pattern]]: Provide a way to visit every node in a hierarchical [[data structure]] such as a tree.
{{Reflist}}
▲* [[Scheduled-task pattern]]: A task is scheduled to be performed at a particular interval or clock time (used in [[real-time computing]])
==See also==
Line 29 ⟶ 58:
* [[Concurrency pattern]]
<!--Categories-->
▲==References==
[[Category:Software design patterns]]
<!--Interwikis-->
[[bs:Šema ponašanja]]
[[hu:Viselkedési minta]]
| |||