CSC/ECE 517 Spring 2014/ch1 1w1l m: Difference between revisions
Jump to navigation
Jump to search
(Created page with "= Design Patterns Involving Closures = == Background == == Examples ==") |
No edit summary |
||
| Line 2: | Line 2: | ||
== Background == | == Background == | ||
=== What is a closure? === | |||
According to Peter Norvig's <ref>[http://norvig.com/design-patterns/design-patterns.pdf Design Patterns in Dynamic Languages]</ref>, closures can be considered "behaviors with attached state data and without the overhead of classes." This is the inverse of objects, which are state data with behaviors attached, and closures encapsulate local state variables. | |||
== Examples == | == Examples == | ||
== Narration == | |||
== Links to Important Terms == | |||
== References == | |||
<references /> | |||
Revision as of 02:52, 17 February 2014
Design Patterns Involving Closures
Background
What is a closure?
According to Peter Norvig's <ref>Design Patterns in Dynamic Languages</ref>, closures can be considered "behaviors with attached state data and without the overhead of classes." This is the inverse of objects, which are state data with behaviors attached, and closures encapsulate local state variables.
Examples
Narration
Links to Important Terms
References
<references />