Closures

From APIDesign

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 λ-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 overwhelming ecstasy in the Java community I decided to write this page and provide few insights from less conventional angles.

The Da Vinci Closures

Everyone who read or saw The Da Vinci Code knows that those who rule the world need to be taken with a grain of salt. Those can never describe the real estate of things, they need to hide them behind multiple meanings, make trustable untrustable and untrustable real. Using irony and self denying references is good. Those who discover part of the truth can never know whether it is the grail or just a fake layer of completely opposite meaning.

To be continued...