|
Thanks Clément. Making that setting change, then "Compiler recompileAll" did fix the problem. However following up with "OpalCompiler recompileAll" does not reintroduce the problem. Starting again with a fresh build #30564, I confirmed the problem was there, then first did "OpalCompiler recompileAll" and the problem remained. btw, (sorry) a correction below, the place to insert the breakpoint was SpecLayout>>privateAsArray not SpecRowLayout>>privateAsArray. regards, Ben Clément Bera wrote: There is a bug left in double nested blocks in the debugger (some variables then shows incorrect value).Retry with the old compiler (world menu>settings>compiler>Compiler) and see if this is fixed. 2013/11/11 Max Leske <[email protected]>Not sure if it’s related to your issue but I’ve been seeing swapped temporary variables in the debugger. The value used for execution is correct but in the view two variables will have the value of the other. Are you sure that the value *effectively* changes or could it be a visualization problem? Max On 11.11.2013, at 17:29, [email protected] wrote: |
- [Pharo-dev] Unexpected block variable change of value btc
- Re: [Pharo-dev] Unexpected block variable change of val... Max Leske
- Re: [Pharo-dev] Unexpected block variable change of... Clément Bera
- Re: [Pharo-dev] Unexpected block variable chang... btc
- Re: [Pharo-dev] Unexpected block variable c... Clément Bera
