<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 18, 2012, at 9:49 PM, Jay K wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: Tahoma; font-size: 13px; ">LLVM isn't a bad idea, but there is more expertise out there (and in me) with C and C++, so C and C++ are easier to generate.<br>It is a bit of a chore to learn and use.<br> <br> <br>JIT isn't a crazy idea either..or rather, an interpreter.<br>If you look at parse.c..and you add a few thread locals..I think it's not hard to turn it into an interpreter.<br> (In reality you don't want to start with parse.c because of the GPL.)</span></span></blockquote></div><br><div>LLVM and JIT are close enough. You do LLVM, you get JIT.</div><div><br></div><div>Also, for debugging we need DWARF. Not incompatible with LLVM. </div></body></html>