<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Volatile keyword</title>
	<atom:link href="http://www.gerbrand-ict.nl/2009/04/volatile-keyword/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gerbrand-ict.nl/2009/04/volatile-keyword/</link>
	<description>Weblog on JEE and software-engineering</description>
	<lastBuildDate>Sun, 20 Nov 2011 17:59:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: gerbrand</title>
		<link>http://www.gerbrand-ict.nl/2009/04/volatile-keyword/comment-page-1/#comment-11814</link>
		<dc:creator>gerbrand</dc:creator>
		<pubDate>Fri, 15 Apr 2011 07:22:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.gerbrand-ict.nl/?p=191#comment-11814</guid>
		<description>Hello Marcel,

Great to hear of you. In the Java world using volatile (assuming the keyword has the same meaning), as well as writing multi-threaded code in a direct way (which you&#039;re doing then) is by many considered something you should do as little as possible by some.

Many however still do, I&#039;ve seen quite some crappy java code where people wrote their own scheduler, tried to make code optimized for multicore, creating threads themselves. In the end they had badly working functionality that would have worked out of the box if they&#039;d chosen an existing framework instead.

I&#039;ve fixed the link so you can view the presentation again. Fixed some spelling errors too.</description>
		<content:encoded><![CDATA[<p>Hello Marcel,</p>
<p>Great to hear of you. In the Java world using volatile (assuming the keyword has the same meaning), as well as writing multi-threaded code in a direct way (which you&#8217;re doing then) is by many considered something you should do as little as possible by some.</p>
<p>Many however still do, I&#8217;ve seen quite some crappy java code where people wrote their own scheduler, tried to make code optimized for multicore, creating threads themselves. In the end they had badly working functionality that would have worked out of the box if they&#8217;d chosen an existing framework instead.</p>
<p>I&#8217;ve fixed the link so you can view the presentation again. Fixed some spelling errors too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcel Veldhuizen</title>
		<link>http://www.gerbrand-ict.nl/2009/04/volatile-keyword/comment-page-1/#comment-11809</link>
		<dc:creator>Marcel Veldhuizen</dc:creator>
		<pubDate>Fri, 15 Apr 2011 05:08:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.gerbrand-ict.nl/?p=191#comment-11809</guid>
		<description>I don&#039;t know how volatile is regarded in the Java world, but in .NET it is considered harmful by some. Not in the least because most people are uncertain whether it&#039;s enough to use a volatile variable, and when to use a memory barrier.

Unfortunately the link to the presentation by Peter Veentjer seems to be dead.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know how volatile is regarded in the Java world, but in .NET it is considered harmful by some. Not in the least because most people are uncertain whether it&#8217;s enough to use a volatile variable, and when to use a memory barrier.</p>
<p>Unfortunately the link to the presentation by Peter Veentjer seems to be dead.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

