<?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 handling sometimes overly volatile</title>
	<atom:link href="http://shape-of-code.coding-guidelines.com/2009/03/02/volatile-handling-sometimes-overly-volatile/feed/" rel="self" type="application/rss+xml" />
	<link>http://shape-of-code.coding-guidelines.com/2009/03/02/volatile-handling-sometimes-overly-volatile/</link>
	<description></description>
	<lastBuildDate>Sun, 12 Feb 2012 22:01: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: Shantanu Goel</title>
		<link>http://shape-of-code.coding-guidelines.com/2009/03/02/volatile-handling-sometimes-overly-volatile/comment-page-1/#comment-200</link>
		<dc:creator>Shantanu Goel</dc:creator>
		<pubDate>Tue, 10 Mar 2009 05:15:14 +0000</pubDate>
		<guid isPermaLink="false">http://shape-of-code.coding-guidelines.com/?p=74#comment-200</guid>
		<description>Derek, 
Thanks for visiting safercode. Your blog is quite interesting and i&#039;d surely be watching the feed for more articles like this. I&#039;m particularly interested in the C standard vs implementation details that your articles have.
It is true that volatiles are quite dangerous beasts, which is why we don&#039;t use them at all in our code at my company (and we produce humungous amounts of code for embedded devices).
For code base, you could look at some of the devices which have open-sourced their firmwares (like Asus WL-500W routers) but in most of these cases, they are based on linux kernel which again doesn&#039;t use much volatiles (all the kernel developers detest it)</description>
		<content:encoded><![CDATA[<p>Derek,<br />
Thanks for visiting safercode. Your blog is quite interesting and i&#8217;d surely be watching the feed for more articles like this. I&#8217;m particularly interested in the C standard vs implementation details that your articles have.<br />
It is true that volatiles are quite dangerous beasts, which is why we don&#8217;t use them at all in our code at my company (and we produce humungous amounts of code for embedded devices).<br />
For code base, you could look at some of the devices which have open-sourced their firmwares (like Asus WL-500W routers) but in most of these cases, they are based on linux kernel which again doesn&#8217;t use much volatiles (all the kernel developers detest it)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

