Eliot Miranda-2 wrote:
>
> with closures the block in allSubInstances will be a different object on
> each evaluation. Pre closures this would have been a single BlockContext
> used for each evaluation of the block (and hence non-reentrant). So you
> need to modify, e.g. by implementing allIn
Yes I checked that too.
BTW thanks - this is nice to open a bug tracker entry because like that we do
not have open it
just to close it. :)
>>>
> I think the fixed bug was the similar 'Issue 1044:MethodContext
> allInstances loops forever'. Not quite the same:
>
> 'From Pharo1.0beta of 16 M
Stéphane Ducasse wrote:
>
> thanks eliot
>
> this is strange I thought that we fixed that already I have to check.
>
> On Dec 18, 2009, at 6:28 PM, Eliot Miranda wrote:
>
>> with closures the block in allSubInstances will be a different object on
>> each evaluation. Pre closures this
thanks eliot
this is strange I thought that we fixed that already I have to check.
On Dec 18, 2009, at 6:28 PM, Eliot Miranda wrote:
> with closures the block in allSubInstances will be a different object on each
> evaluation. Pre closures this would have been a single BlockContext used
with closures the block in allSubInstances will be a different object on
each evaluation. Pre closures this would have been a single BlockContext
used for each evaluation of the block (and hence non-reentrant). So you
need to modify, e.g. by implementing allInstancesDo: in MethodContext class:
'
Pharo image: Pharo | Pharo-core
PharoCore1.0rc1 Latest update: #10502
VM: unix - i686 - linux-gnu - Pharo0.1 of 16 May 2008 [latest update:
#10074]
Steps to reproduce:
1.Object allSubInstances
It appears to be repeatedly adding its current context.
...Stan
OrderedCollection>>addLast:
