1:25:05drmeisterWell, that's a bit of a puzzler isn't it? With compile-file we use the literal compiler to generate code that evaluates to initialize the literals vector.
1:25:28drmeisterThat's a whole other virtual machine that we have.
1:25:46drmeisterWe will have to interface with that.
1:26:13drmeisterHere's what I think will happen - does it sound true?
1:26:23drmeisterWe implement COMPILE with the bytecode compiler.
1:26:59drmeisterIt loads and compiles all of the bclasp source code and clos and then the cleavir code.
1:27:10drmeisterWe then run the cleavir compiler to compile-file everything.
1:28:40drmeisterLater we can interface the literal compiler with the bytecode compiler - but will we need to translate the literal compiler into C++?
1:29:46drmeisterOr I'm misunderstanding the problem - or making it larger than it is.
1:33:40Bikei kind of thought we'd be compile-filing with the bytecode compiler, but i haven't deeply thought it through
1:51:57drmeisterWhen we compile with the bclasp compiler or the cclasp compiler we do different things with literals than we do with compile-file. I guess we should look at that.
1:52:49drmeisterI've been thinking of the bytecode compiler/interpreter as a replacement for the C++ interpreter.
1:53:57drmeisterThe bytecode compiler is building a literals/const vector - right?