<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Aug 31, 2009, at 1:19 PM, Renato Golin wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; 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; ">2009/8/31 Axel Naumann <<a href="mailto:Axel.Naumann@cern.ch">Axel.Naumann@cern.ch</a>>:<br><blockquote type="cite">we want to implement a C++ interpreter using LLVM and clang<br></blockquote><br>Isn't clang going on that direction anyway?<br><br>cheers,<br>--renato</span></blockquote></div><br><div>Building a C++ interpreter involves a substantial amount of work beyond building a working C++ frontend and code generator (translation to LLVM IR). I think Axel was referring to the work on the interpreter itself, which would build on top of the work-in-progress C++ support in Clang.</div></body></html>