Re:Parallel Programming: I Told You So
by JulianMorrison on Wednesday September 16, 2009 @10:29AM
(#825850)
"C blocks" == closures?
[ Parent
| on HN ]
They don't sound far off. Wikipedia agrees with you so far :)
http://en.wikipedia.org/wiki/Blocks_%28C_language_extension%...
The Ars Technica review of Snow Leopard features a nice introduction to the new language feature:
http://arstechnica.com/apple/reviews/2009/08/mac-os-x-10-6.a...
Re:Parallel Programming: I Told You So
by silentbicycle on Wednesday September 16, 2009 @10:58AM
(#825929)
They're immutable, though. (For sake of parallelization.)
Proper closures in a pure language are immutable, too.
Re:Parallel Programming: I Told You So
by silentbicycle on Wednesday September 16, 2009 @12:27PM
(#826148)
Well, sure, but that's not usually what people are talking about when they mean closures.
Depending on how pure the language is, /variables/ can be immutable. Nonetheless, the standard, default, run-of-the-mill variables that most programmers will run into most of the time are not. Same goes for closures.
Re:Parallel Programming: I Told You So
by JulianMorrison on Wednesday September 16, 2009 @11:11AM
(#825942)
Pretty similar to Java anonymous inner instances of Runnable and Callable, then.
Except those can't read nor modify variables in their enclosing scope. Anonymous inner instances are more akin to C's nested functions, which GCC has had for a long time.
Correct me if I'm wrong though (which would only make me very happy); been years since I did Java.
Re:Parallel Programming: I Told You So
by JulianMorrison on Thursday September 17, 2009 @05:51AM
(#827730)
They can read and modify object fields in their outer class's instance. But it's true they can't modify stack variables. This makes contextual sense - C blocks are being stack allocated and have to be explicitly copied to the heap. Java inner instances get copied immediately, because everything lives on the heap in Java.