<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 08 Oct 2010, at 22:45, Andrew Brunner wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Monaco; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">On Fri, Oct 8, 2010 at 3:37 PM, Marco van de Voort <<a href="mailto:marcov@stack.nl">marcov@stack.nl</a>> wrote:<br><blockquote type="cite">No, but the last one might be set before the condition coupled to that last<br></blockquote><blockquote type="cite">one might be carried out. See Jonas' example.<br></blockquote><br>The ONLY way that could happen is if the boolean happens to be set in<br>a worker thread's method that still has more work to do.</span></blockquote><br></div><div>That is incorrect. Even if you set the boolean only to true at the very end, problems can still occur. See e.g. <a href="http://en.wikipedia.org/wiki/Memory_barrier#An_illustrative_example">http://en.wikipedia.org/wiki/Memory_barrier#An_illustrative_example</a> for an example and explanation.</div><div><br></div><div><br></div><div>Jonas</div><br></body></html>