Thanks.
Ok This is clear now - the outerContext is like my scheme environment.
This is what I was thinking but the examples I was trying (stupidly) where just
passing
the block as argument to different methods and they were not changing the
outerContext :)
Clement will write some class
I wrote some class comments, but somehow it cannot be merged in Pharo in a
normal way.
Warning: 'You should not change blockclosure' or something like that
I will check with Marcus later.
2013/7/25 Stéphane Ducasse stephane.duca...@inria.fr
Thanks.
Ok This is clear now - the outerContext is
For the people following I added a test to show the homeContext of a block
| homeContext b1 |
homeContext := thisContext.
b1 := [| b2 |
self assert: thisContext closure == b1.
self assert: b1 outerContext == homeContext.
self assert: b1 home = homeContext.
Perhaps you should add some value message so that the assertions are
actually run, shouldn't you ?
2013/7/25 Stéphane Ducasse stephane.duca...@inria.fr
For the people following I added a test to show the homeContext of a block
| homeContext b1 |
homeContext := thisContext.
b1 := [| b2 |
On 25 juil. 2013, at 13:12, Clément Bera wrote:
Perhaps you should add some value message so that the assertions are actually
run, shouldn't you ?
I always felt that e-mails lack an unsend command :D
2013/7/25 Stéphane Ducasse stephane.duca...@inria.fr
For the people following I added a
On Thu, Jul 25, 2013 at 1:17 PM, Camille Teruel camille.ter...@gmail.comwrote:
On 25 juil. 2013, at 13:12, Clément Bera wrote:
Perhaps you should add some value message so that the assertions are
actually run, shouldn't you ?
I always felt that e-mails lack an unsend command :D
Or gmail
:)
On Jul 25, 2013, at 1:20 PM, Guillermo Polito guillermopol...@gmail.com wrote:
On Thu, Jul 25, 2013 at 1:17 PM, Camille Teruel camille.ter...@gmail.com
wrote:
On 25 juil. 2013, at 13:12, Clément Bera wrote:
Perhaps you should add some value message so that the assertions are
