Lisp to C compiler

Hi! It is me again!

I've found that continuations in C/C++ doesn't require tail-call optimization on the part of the compiler. You can just do setjmp and longjmp when stack gets close to full. This means you can't do stack allocation, but you should allocate everything on heap anyway.

>>10

when the stack is blown, copy all live data to the heap.

How does runtime know the C/C++ stack frame format? Then again, some arguments are passed in registers (fastcall convention) and function can be inlined, so a simple longjmp would lost it. I know GDB parses it somehow to get stack trace, but only if debugging info is present.