Lightweight bytecode interpreter

JeffBezanson 494e439510 using lisp value stack for call frames instead of the C stack ... adding the ability to grow the value stack as needed the net effect is that calls use much less space, and stack frames can use all available heap space. the only downside is that C builtins must be aware that the stack can change out from under them if they call lisp code. currently the only example of this is table.foldl. also fixing bug where exceptions failed to unwind the gc handle stack.		2009-07-03 18:43:15 +00:00
femtolisp	using lisp value stack for call frames instead of the C stack	2009-07-03 18:43:15 +00:00
llt	tiny performance tweaks: removing some variables, making some static	2009-06-09 18:46:02 +00:00