Make a new interpreter #2

New Issue

haxala1r · 2026-02-05T19:32:17Z

haxala1r commented

2026-02-05 19:32:17 +00:00

The current interpreter (the one in the main branch as of now) is no longer actually connected to the language being compiled in the compiler branch. A new interpreter should take its place, however this time instead of having completely separate code from the compiler, the new interpreter should use either the Core AST or the AST generated after the closure conversion process. This would help in debugging the AST, as any problems in generating the AST would show up in the interpreter as well as the rest of the compiler, whereas any code generation/execution problems would be limited to the compiler.

This is related to #1 as proper scope analysis is required for an interpreter as much as it is required for the compiler.

The current interpreter (the one in the main branch as of now) is no longer actually connected to the language being compiled in the compiler branch. A new interpreter should take its place, however this time instead of having completely separate code from the compiler, the new interpreter should use either the Core AST or the AST generated after the closure conversion process. This would help in debugging the AST, as any problems in generating the AST would show up in the interpreter as well as the rest of the compiler, whereas any code generation/execution problems would be limited to the compiler. This is related to #1 as proper scope analysis is required for an interpreter as much as it is required for the compiler.

haxala1r self-assigned this 2026-02-05 19:32:17 +00:00

haxala1r added this to the olisp project 2026-02-05 19:32:17 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: haxala1r/olisp#2