Closure (computer science): Difference between revisions
Jump to navigation
Jump to search
imported>Pat Palmer (draft 2) |
imported>Pat Palmer (draft 3) |
||
| Line 1: | Line 1: | ||
A '''closure''' is a capability of certain [[programming language|programming languages]]. As with many terms relating to [[software]], there are conflicting definitions of closure within the field of [[computer science]]. According to [[Martin Fowler]]: "Some people say that the term only applies to an actual value that includes bindings from its environment...Others use the term 'closure' to refer to a programming construct that has the ability to bind to its environment." | A '''closure''' is a capability of certain [[programming language|programming languages]]. As with many terms relating to [[software]], there are conflicting definitions of closure within the field of [[computer science]]. According to [[Martin Fowler]]: "Some people say that the term only applies to an actual value that includes bindings from its environment...Others use the term 'closure' to refer to a programming construct that has the ability to bind to its environment."<ref name="MF">{{cite web|url=http://martinfowler.com/bliki/Closure.html|title="Closure"|publisher=© Copyright Martin Fowler, all rights reserved|year=2007|accessdate=2007-09-17}}</ref> | ||
Revision as of 20:34, 17 September 2007
A closure is a capability of certain programming languages. As with many terms relating to software, there are conflicting definitions of closure within the field of computer science. According to Martin Fowler: "Some people say that the term only applies to an actual value that includes bindings from its environment...Others use the term 'closure' to refer to a programming construct that has the ability to bind to its environment."[1]