<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Mar 11, 2013 at 5:59 PM, Eliot Miranda <span dir="ltr"><<a href="mailto:eliot.miranda@gmail.com" target="_blank">eliot.miranda@gmail.com</a>></span> wrote:<br>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">No. Its arguably a bug but a binding will print itself as the Symbol key. So what's happening is that the binding for DateAndTime is printing itself as #DateAndTime. So the problem is that the Decompiler is not mapping the sequence pushLiteral: aBinding, send #value back into an appropriate LiteralVariableNode instance. The Decompiler needs to special-case this.</blockquote>
<div><br></div><div>Yeah, that should probably be fixed. The new Alias bindings will generate #value sends, which I don't think we've used before. (We've used #value: for assignment to globals, but not #value for reads.) </div>
<div><br></div><div>But since DateAndTime is a class, this shouldn't be an Alias at all, and thus shouldn't be sending #value. </div><div><br></div><div>Colin</div></div></div></div>