Continuing with the study of functional programming, these are my recent links about closures:
In computer science, a closure (also lexical closure, function closure or function value) is a function together with a referencing environment for the nonlocal names (free variables) of that function. Such a function is said to be "closed over" its free variables. The referencing environment binds the nonlocal names to the corresponding variables in scope at the time the closure is created, additionally extending their lifetime to at least as long as the lifetime of the closure itself.
The concept of closures was developed in the 1960s and was first fully implemented as a language feature in 1975 in the programming language Scheme to implement lexically-scoped first-class functions. Since then, many languages have been designed to support closures.
Closures – A Simple Explanation (Using Ruby)
Cerraduras: clojure en español: Qué es una closure
Yes! AjSharp has closures
InfoQ: Lambdas in Java: An In-Depth Analysis
Closures – lambdaj – How lambdaj 2.0 brings (almost) real closures to Java
Scala function objects from a Java perspective
newLISP – Closures
Tailcall anyone ? | Java.net
Groovy Goodness: Splitting with Closures – Messages from mrhaki
Tennent’s Correspondence Principle and Returning From a Closure
Code rant: C# Closure Constructors
Groovy vs. Scala – We Need a Closure… « GridGain – Cloud Development Platform
InfoQ: Mark Reinhold on Closures for Java
I should review the current state
Closures as a Response to Multi-core Processors? | Java.net
Closures are back again!
C# in Depth: The Beauty of Closures
Functional programming in the Java language
RE: What’s so cool about Scheme?
InfoQ: Language Parity: Closures and the JVM
Practically Groovy: Functional programming with curried closures
Closures + Lambda = The key to OOP in Lisp « Learning Lisp
Did it with .NET – What’s In A Closure?
Did it with .NET – Fibonacci Numbers, Caching and Closures
Closures and Continuations
Keep tuned, more to come!