<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: JavaOne: Cliff Click on Data Races</title>
	<link>http://tech.puredanger.com/2008/05/08/javaone-cliff-click-on-data-races/</link>
	<description>Alex Miller's technical blog</description>
	<pubDate>Sun, 27 Jul 2008 01:12:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: Alex</title>
		<link>http://tech.puredanger.com/2008/05/08/javaone-cliff-click-on-data-races/#comment-46485</link>
		<pubDate>Fri, 09 May 2008 05:36:34 +0000</pubDate>
		<guid>http://tech.puredanger.com/2008/05/08/javaone-cliff-click-on-data-races/#comment-46485</guid>
					<description>Double-checked locking is safe if you make the instance a volatile.  I'm not sure why you think otherwise - Cliff said the same during the talk.</description>
		<content:encoded><![CDATA[<p>Double-checked locking is safe if you make the instance a volatile.  I&#8217;m not sure why you think otherwise - Cliff said the same during the talk.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Lachlan O'Dea</title>
		<link>http://tech.puredanger.com/2008/05/08/javaone-cliff-click-on-data-races/#comment-46401</link>
		<pubDate>Fri, 09 May 2008 00:11:50 +0000</pubDate>
		<guid>http://tech.puredanger.com/2008/05/08/javaone-cliff-click-on-data-races/#comment-46401</guid>
					<description>I could have sworn that I read somewhere that the changes to the memory model in Java 5 meant that double checked locking is now safe if you use volatile. The JVM now has to ensure that no memory access is reordered relative to accesses to volatiles, even absent monitor ownership.</description>
		<content:encoded><![CDATA[<p>I could have sworn that I read somewhere that the changes to the memory model in Java 5 meant that double checked locking is now safe if you use volatile. The JVM now has to ensure that no memory access is reordered relative to accesses to volatiles, even absent monitor ownership.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
