zlacker

> Common Lisp that compiles to Java

To Java bytecode or to Java code?

>>elwell+(OP)
Java _code_. It's madness, though I'm assured it made sense at the time.

>>catpol+31
It makes more sense than generating bytecode since your “compiler” doesn’t need to comply to runtime changes other than high level API compatibility and you can leverage the performance improvements of which ever Java compiler is used to produce the final bytecode.

>>catpol+31
Java code is almost the same as bytecode, and is easier to debug.

That's a benefit of having a VM with JIT.

>>elwell+(OP)
Java code, and then bytecode of course. Gives us meaningful stack traces, among other things.