<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">2014-05-14 21:15 GMT+02:00 Eliot Miranda <span dir="ltr"><<a href="mailto:eliot.miranda@gmail.com" target="_blank">eliot.miranda@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi All,<div><br></div><div> I've moved my VM work from an old Squeak 4.1 image to a trunk-derived 4.5 image and now to a Spur version of that. Remember that Spur has immediate characters. So the stupid thing I did was...</div>
<div><br></div><div>I just published a version of Compiler to trunk form my Spur image. So right now that package's binary component is potentially Spur format. I realised too late and thought "oh s..., maybe I broke trunk". So I started up my non-Spur image and checked that I could successfully load the new Compiler package.</div>
<div><br></div><div> Can anyone who understands the binary scheme inside Monticello packages explain why it "just worked"?<span class="HOEnZb"><font color="#888888"><br clear="all"><div><br></div></font></span></div>
</div></blockquote><div><br></div><div>MCZ also embed a textual source file.<br></div><div>If ever MC fails to decode the binary blob it falls back to decoding the text...<br><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div><span class="HOEnZb"><font color="#888888"><div></div>-- <br>relieved,<div>Eliot</div>
</font></span></div></div>
<br><br>
<br></blockquote></div><br></div></div>