Hi Denis,

No idea why the current debugger is not based on the AST interpreter or if there are any plans to move it.

However, I think it will help to make the��ASTDebugger compatible with the current debugger from Pharo.

From what I see the code from��ASTDebugger is indeed very simple. One option could be to create a subclass

of DebugSession that overrides those methods that control the execution. If this goes easy then we could just

reuse both the Spec and the Glamour UIs.

Do you want to give it a try or sync more on this?

Cheers,

Andrei

On Wed, May 25, 2016 at 12:12 PM, Denis Kudriashov <dionisiydk@gmail.com> wrote:

Hi.

Look at AST-Interpreter project which includes AST-Debugger http://smalltalkhub.com/#!/~Pharo/AST-Interpreter. Code is so simple comparing to "bytecode simulation" approach of current debugger.��
AST debugger are independent from bytecode set. It just visit AST-nodes to simulate code execution.

But current debugger simulates bytecode. It depends on current bytecode set. There are few kinds of BytecodeEncoders. To understand how current debugger is working you need to know many VM details.

So my question is why our debuggers are not based on AST interpreter? Why it is bad idea? (if it is bad).

Best regards,
Denis