proj-oot-ootImplementation3

see also OotMemoryManagement?

"separate heap per lightweight process (hence no stop-the-world GC),"

how much of Oot semantics can be built as a separate library? how much of it can be cleanly accessible to C and Lua programs?

note that if a library uses setjump and longjmp, apparently it becomes less portable due to inferior compiler support on various platforms, and it screws up stack-based RAII in C++ because the stack unwind doesn't happen