On Jun 19, 2013, at 9:35 AM, Sven Van Caekenberghe <[email protected]> wrote:
> > On 19 Jun 2013, at 08:52, Marcus Denker <[email protected]> wrote: > >> >> On Jun 13, 2013, at 2:48 PM, Marcus Denker <[email protected]> wrote: >> >>> >>> On Jun 13, 2013, at 2:23 PM, Sean P. DeNigris <[email protected]> wrote: >>> >>>> Why do we get [...] when Opal is not active? Why can't we keep the old >>>> behavior? >>>> >>> >>> >>> Soon we will switch to Opal, there are just 2 bugs left (that I know of ;-) >>> We where a bit distracted last week so there was no progress on those… soon. >>> >> >> Blocks are now pretty-printed again. >> >> In addition, the new bytecode->AST->source mapping is active, this should >> speed >> up the Debugger a bit and should fix some long standing highlighting bugs. >> >> (But due to the inherent complexity of the whole thing, it fire sure will >> have some >> problems, we will see. The good thing is that problems should be easy to >> debug >> due to the explicit AST/IR based mapping) >> >> Marcus >> > > Yes, for end users, improving the debugger based on Opal should be the next > step. > So what we already have is a first step towards "per AST Node" break/watch/inspect points. Together with the new debugger implementation and the new editor this will allow some quite fancy debugger improvements. Marcus
