Closures
From APIDesign
JaroslavTulach (Talk | contribs)
(New page: Closures are classical OOP approach to represent a block of code that can be invoked passing in few parameters. Closures are typical build...)
Next diff →
Revision as of 16:37, 28 November 2009
Closures are classical OOP approach to represent a block of code that can be invoked passing in few parameters. Closures are typical building block of Smalltalk systems. Origin of closures (called lamdas back then) can however be traced many years into the past to &lamda;-calculus (where there is nothing else than invocable blocks of code).
Since their invention closures become almost mandatory syntactic element for any new language. Not having them become a faux pas. As the profound history of programming languages puts it: Java makes them popular by not having them.
Looks like things are about to change Sun recently announced its will to implement closures for JDK7. To join the mutual extasy in the Java community I decided to write this page and provide few insights from the other side.
To be continued...
Follow
