<br><br><div class="gmail_quote">On Sun, May 30, 2010 at 22:59, Simen kjaeraas <span dir="ltr"><<a href="mailto:simen.kjaras@gmail.com">simen.kjaras@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div class="h5">Simen kjaeraas <<a href="mailto:simen.kjaras@gmail.com" target="_blank">simen.kjaras@gmail.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
How does the current range system accommodate parallel iteration?<br>
<br>
As far as I can see, a context switch could happen between calls to<br>
popFront and front, thus popping a value off the range before we're<br>
able to get its value.<br>
</blockquote>
<br></div></div>
Anyone? It seems to me the system is not thread-safe, and a parallel<br>
range should have the functions lock() and unlock(), so a foreach<br>
would work basically like this:<br></blockquote><div><br>I don't know if that'd help you, but did you have a look at David Simcha's parallelFuture module?<br><br><a href="http://cis.jhu.edu/~dsimcha/parallelFuture.html">http://cis.jhu.edu/~dsimcha/parallelFuture.html</a><br>
<br> <br></div></div>