On Wed, Jun 3, 2009 at 1:46 PM, Abdulaziz Ghuloum <[email protected]> wrote: > All I know is that the ikarus > debugger is pretty straight-forward. It is implemented all > in scheme. It only uses one ikarus-specific feature (call/cf > which gives you an eq?-comparable pointer onto the stack). It > also has a simple interface between the compiler/interpreter > and the debugger, e.g., rewrite all > (proc args ...) > => > (debug-call '<source-info> proc args ...) > and you get debuggable/traceable code.
But how does it work with TCO? In debug mode TCO is disabled or not?
