<br><br><div class="gmail_quote">On Wed, Jun 9, 2010 at 11:51 AM, Andreas Raab <span dir="ltr"><<a href="mailto:andreas.raab@gmx.de">andreas.raab@gmx.de</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 6/8/2010 7:41 AM, David T. Lewis wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
What do the VM developers think with respect adopting the VM changes?<br>
The immutability bit is a scarce resource. Is it OK to allocate it<br>
for this purpose or are there likely to be other projects interested<br>
in using it for other reasons?<br>
</blockquote>
<br></div>
Oh, and one thing that I'm just realizing is that by far the biggest impact of immutability is in primitives and plugins. All primitives in all plugins must be rewritten to test for mutability of the objects they store into before this can work reliably. Ouch.<br>
</blockquote><div><br></div><div>Ouch indeed. One can at least put a check in interpreterProxy to catch attempts and cause primitives to fail. It won't be pretty but will serve as lint for the plugins.</div><div><br>
</div><div>Off the top of your head which plugins are likely to do writes? And which of those are likely to do writes to immutables?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Cheers,<br><font color="#888888">
- Andreas<br>
</font></blockquote></div><br>