<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jan 21, 2013 at 3:51 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 21-01-2013, at 3:48 PM, Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com">eliot.miranda@gmail.com</a>> wrote:<br>
><br>
> Alas it bites at a slightly higher-level than that also. Yes, the decoupling of positioning and reading is a problem for thread-safety. But so is the single buffer and the single position. e.g. if one were to call your unified primitive below to fill the buffer that wouldn't prevent another thread reading at a different position into the same buffer and trashing the contents from the POV of the first thread. Since the programming tools are essentially single-threaded it's not *that* bad a problem, unless you're debugging source access (I *think*).<br>
<br>
</div>Gotta start somewhere. Bottom is often good. Then other people can build upon that.<br></blockquote><div><br></div><div>Sure, but can't solve the immediate problem this way because it takes time for a VM change to percolate through. </div>
</div>-- <br>best,<div>Eliot</div>
</div></div>