You don't understand what a closure is, so this question makes no sense at all, as well as your goal.
Closure is not something which can be "evaluated". This is a union of a function with its
reference environment. The essence of it is to allow the delegate to access the local variables even after the code creating the delegate instance goes out of the scope. In other words,
closure is not some particular object you can obtain or access, this is, at the level of its implementation, a set of internal structures which supports the conception technically. You can read about it here:
http://en.wikipedia.org/wiki/Closure_%28computer_science%29[
^].
If you have some local (stack) variable which is referenced by some
anonymous delegate instance, the code related to access to this variable is modified the way to provide access to its object for all the time when reachability of that delegate instance is kept in the application.
It's very easy to demonstrate the effect of a closure on a .NET example, but I'm not sure if you need that.
—SA