Comments on: Closures in C#: Variable Scoping and Value Types vs Reference Types

By: Foobar

Foobar — Sun, 26 Feb 2012 23:46:00 +0000

the code blocks are all truncated..

By: derick.bailey

derick.bailey — Tue, 24 Feb 2009 14:53:11 +0000

@Freddy,

with a proper understanding of references vs. value types – how values are stored on the stack and how references are pointers on the stack that point to the heap – there is little to no difference in the behavior of values vs references in closures.

however, if a person doesn’t understand the distinction between a value type and a reference type, they may think that the referenced object will be copied in the same way a value type will, which is incorrect.

i was trying to illustrate this difference, really. not sure i accomplished that, though.

By: Freddy

Freddy — Tue, 24 Feb 2009 14:40:02 +0000

Note that scoping the value type inside the loop behaves the same as the reference type:

for (int i = 0; i < = 3; i++)
{
int copy = i;
Func foo = (() => { return copy; });
theActions.Add(foo);
}

I only read it quickly, but I am not sure there is really nothing different on the reference vs. value behavior for closures in C#.

By: Kpullin

Kpullin — Tue, 24 Feb 2009 04:33:47 +0000

@fernando – you can use two fingers to scroll around in the code block (div?). It is awkward and an anoying user experience, but it does work.

By: Fernando

Fernando — Mon, 23 Feb 2009 22:05:48 +0000

I wish safari on the iPhone would allow me to see the code blocks. I mean can see them but only partially not the whole block. I can’t even scroll.