[Pharo-dev] is this ok?
marcus.denker at inria.fr
Sat Nov 23 05:50:18 EST 2013
On 22 Nov 2013, at 20:16, Clément Bera <bera.clement at gmail.com> wrote:
> Well this had been here for a while. I discovered it because it was triggered :). But it is very rare that this is triggered.
> Now when I look into the latest Pharo 3, this halt is not present. So I guess Andrei fixed it when we switched to the new debugger.
No, I removed the halt when I added the “willCreateBlock” to the checks. (In the past blocks where created with message sends, so #willSend
made sure that the loop terminated in front of the block, now it runs over the block creation code…).
> 2013/11/22 Esteban Lorenzano <estebanlm at gmail.com>
> in the debugger:
> "Simulate the execution of bytecodes until either sending a message or
> returning a value to the receiver (that is, until switching contexts)."
> | context |
> [ self willSend or: [ self willReturn or: [ self willStore ] ] ]
> whileFalse: [
> context := self step.
> context == self ifFalse: [
> self halt. "<========================= THIS"
> "Caused by mustBeBoolean handling"
> ^context ]]
> so... the halt is ok there?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pharo-dev