These should be informative:
http://www.mirandabanda.org/cogblog/2008/06/07/closures-part-i/
http://www.mirandabanda.org/cogblog/2008/07/22/closures-part-ii-the-bytecodes/
http://www.mirandabanda.org/cogblog/2008/07/24/closures-part-iii-the-compiler/
On Tue, Aug 6, 2013 at 2:14 PM, Louis LaBrund
Hi Guys,
FWIW, VA Smalltalk doesn't allow changing block arguments.
Lou
On Tue, 6 Aug 2013 13:42:33 -0700, Casey Ransberger
wrote:
>I didn't read your post clearly enough. Yep, that would seem odd. You may
>have a bug there. I'm not sure why that happens. It looks like the outer
>context isn't
I didn't read your post clearly enough. Yep, that would seem odd. You may
have a bug there. I'm not sure why that happens. It looks like the outer
context isn't taking the assignment, but hanging onto the initial value it
receives from #value:.
I'm not totally sure we should expect to be able to d
Hi, Casey
It'll be great if you can tell the name of the parameter.
The assignment to block argument does actually work with no error. So it
looks like "allow block argument assignment" parameter is enabled. Here is
the example:
[:x | x := x + 1. x] value: 1 => 2
But as we can see from example
