<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 1, 2014 at 6:49 AM, David T. Lewis <span dir="ltr"><<a href="mailto:lewis@mail.msen.com" target="_blank">lewis@mail.msen.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Currently we have this:<br>
<br>
Binding>>objectForDataStream: refStream<br>
"It's not yet clear how serialization should work in the presence of environments"<br>
self shouldBeImplemented.<br>
<br>
A Binding seems to be a simple object. Does it really need special handling<br>
when serializing?<br></blockquote><div><br></div><div>It does. If you write a binding out to disk and then read it back in, you should have the same instance you started with, and not a copy. That part is fairly straight-forward: we include just the key in the data stream, and then when reading it back in we fetch the binding using the key.</div>
<div><br></div><div>For now, the simple thing is just to use "Environment current" when we need to lookup a binding. At some point we'll need a way to specify which environment to use when reading objects from disk, but that needn't stand in the way of getting this working again. </div>
<div><br></div><div>Colin</div></div></div></div>