12:45:45drmeisterI think we should implement the interpreter straight into c++. In Common Lisp it will be weird and require more functions to be exposed.
12:46:21jackdanieldrmeister: common lisp interpreter?
18:06:03Colleenkarlosz: drmeister said 17 hours, 26 minutes ago: I just realized I'd need to expose stack manipulation functions, closure slot accessing functions, and multiple-value accessing functions if we want to implement the VM in Common Lisp for testing. Should I?
18:06:22karloszdrmeister: no, i don't think a VM in CL on Clasp is necessary
18:06:37karloszwe should go straight to C++ ot write it.
18:07:08karloszwe already have an implementation independent prototype vm for the bytecode machine which does weird stuff like emulate pointers and pointer arithmetic with array indices. it's not great
18:07:28karloszinterior pointers into the stack/bytecode array/literals array make way more sense in C++
18:07:46karloszin other news i have keyword parsing implemented and working now
18:07:56karlosz&aux is just LET* right? we don't have that yes