On Apr 19, 2013, at 12:34 PM, Marcus Denker wrote: > > On Apr 19, 2013, at 12:10 PM, Henrik Johansen <henrik.s.johan...@veloxit.no> > wrote: > >> >> On Apr 19, 2013, at 9:37 AM, Marcus Denker wrote: >> >>> Maybe of general interest… >>> >>> >>> Begin forwarded message: >>> >>>> Hi, >>>> >>>> These just work with Opal correctly: >>>> >>>> 7202 Errors when debugging inlined values >>>> https://pharo.fogbugz.com/f/cases/7202 >>>> >>>> 750 Debugger highlight bug >>>> https://pharo.fogbugz.com/f/cases/750 >>>> >>>> :-) >>>> >>>> Marcus >>> >>> >>> (The list is here: >>> >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-compiler >>> >>> but this is more for boring things, e.g. commits to the repo and issue >>> tracker status mails) >>> >>> Marcus >> Oooooh, I *hate* 750! >> >> Tested it (ClosureTests new testToDoOutsideTemp -> debug) in the latest >> nightly, after switching to Opal the to:do: scope was indeed highlighted >> correctly :D >> .. however, I could not go into/over/through without incorrect >> highlighting/eventual error, I presume that is what the fix mentioned in >> issue coming later today is for? > > Did you use > > https://ci.inria.fr/rmod/job/Opal/ > > The Opal in the image is a bit out-dated…
I did just now, but there, debugging *anything* (even 3 + 4, or using cmd dot) with the Opal Compiler set to default seemed to bring the image into a near catatonic state… Sort of hard to check if the buttons were fixed, with no debugger ever opening. ;) Cheers, Henry
