<br><br><div class="gmail_quote">On Sat, Oct 31, 2009 at 2:09 AM, Marcus Denker <span dir="ltr"><<a href="mailto:denker@acm.org">denker@acm.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="word-wrap: break-word;"><div class="im"><br><div><div>On Oct 28, 2009, at 3:50 AM, Michael van der Gulik wrote:</div><br><blockquote type="cite">Hi NewCompiler people.<br><br>Does anybody use this compiler as their main one?<br>
<br>I notice that the NewCompiler packages don't override Behavior>>compilerClass. I tried using the ClosureCompiler instead, and it seems to work for some simple classes. Is it not stable enough to use by default?<br>
<font color="#000000"><font color="#144fae"><br></font></font></blockquote><br></div></div><div>Hello,</div><div><br></div><div>On which version of Squeak / Pharo do you plan to use it? </div></div></blockquote><div><br>Anything which works... I don't really care which version is used.<br>
<br>I'm currently using Squeak 3.10, but I can easily move my code to Pharo. <br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="word-wrap: break-word;"><div><br></div><div>The problem is that the version that can emit code for Eliots closures is not yet done. But Jorge made</div><div>lots of progress... we should have something ready soon.</div>
<div><br></div><div>Normally the answer is this: there is a preference (as Math already mentioned). The ClosureCompiler</div><div>class is for tests and for cases where one only wants to use the new compiler on single classes.</div>
<div>(e.g. because it is used for experiments).</div><br clear="all"></div></blockquote></div><br>Excellent.<br><br>I'm going to be making some changes to the compiler:<br><br>* Accept $. in literal names so that namespaces will work. <br>
* Make it use my own implementation of IRBuilder.<br>These two changes are minor and SecureSqueak specific. I'll need to investigate tool support for keeping a "branch" of the new compiler while still being able to commit fixes back to you.<br>
<br>I'll be integrating IRBuilder and all the compilation steps after it as a core part of SecureSqueak. "Class" will be modified to store IR as well as bytecodes. IR will be used to move CompiledMethods across the network in a way that doesn't depend on the VM implementation or bytecode set.<br>
<br>I'll also be making changes to the debugger, but this might mean making a fork of the debugger which is incompatible with Pharo.<br><br>Gulik.<br><br>-- <br><a href="http://gulik.pbwiki.com/">http://gulik.pbwiki.com/</a><br>