<div dir="ltr">Hi Tim,<div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Sep 19, 2013 at 7:27 PM, tim Rowledge <span dir="ltr"><<a href="mailto:tim@rowledge.org" target="_blank">tim@rowledge.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
On 19-09-2013, at 6:20 PM, Nicolas Cellier <<a href="mailto:nicolas.cellier.aka.nice@gmail.com">nicolas.cellier.aka.nice@gmail.com</a>> wrote:<br>
<br>
> There are more clean ups coming soon, when i'll figure out the right order to not break the update stream:<br>
<br>
</div>I'm not familiar enough with how the Compiler is structured these days but thank you for working on tidying it up.<br>
Suggestion; rather than specialised messages try a subclass of Compiler that deals with interactive use and another for batch use. Unless that is what it does already, in which case ignore me ;-)<br></blockquote><div><br>
</div><div>One of the nice improvements is to ditch compilerClass, parserClass et al in favour of newCompiler, newParser, which can then allow exotic initialization etc.</div><div>Compilation cues provide a much nicer way of providing input context to the compiler.</div>
<div>The BytecodeEncoder backend now insulates the compiler from bytecode encoding and hence supports multiple bytecode sets (in use here at Cadence and needing to be more generally released when time allows).</div><div><br>
</div><div>I think these are the big improvements over recent years.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
tim<br>
--<br>
tim Rowledge; <a href="mailto:tim@rowledge.org">tim@rowledge.org</a>; <a href="http://www.rowledge.org/tim" target="_blank">http://www.rowledge.org/tim</a><br>
Error 13: Illegal brain function. Process terminated.<br>
<br>
<br>
<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>best,<div>Eliot</div>
</div></div>