<?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: Coding Standard Rule #6: Use C99&#8242;s Fixed-Width Integer Type Names</title>
	<atom:link href="http://embeddedgurus.com/barr-code/2009/03/coding-standard-rule-6-use-c99s-fixed-width-integer-type-names/feed/" rel="self" type="application/rss+xml" />
	<link>http://embeddedgurus.com/barr-code/2009/03/coding-standard-rule-6-use-c99s-fixed-width-integer-type-names/</link>
	<description>A Blog by Michael Barr</description>
	<lastBuildDate>Fri, 18 May 2012 17:16:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Michael Burr (not Barr)</title>
		<link>http://embeddedgurus.com/barr-code/2009/03/coding-standard-rule-6-use-c99s-fixed-width-integer-type-names/comment-page-1/#comment-44</link>
		<dc:creator>Michael Burr (not Barr)</dc:creator>
		<pubDate>Sat, 02 May 2009 05:01:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfcdev.org/test-stack/2009/03/31/coding-standard-rule-6-use-c99s-fixed-width-integer-type-names/#comment-44</guid>
		<description>Indeed - coming up with your own stdint.h to use when you have a toolset that doesn&#039;t have it isn&#039;t very hard.I have one that I borrowed and modified from the public domain one in the MinGW toolchain. Also, Paul Hsieh has a portable one with a BSD license:  http://www.azillionmonkeys.com/qed/pstdint.h</description>
		<content:encoded><![CDATA[<p>Indeed &#8211; coming up with your own stdint.h to use when you have a toolset that doesn&#8217;t have it isn&#8217;t very hard.I have one that I borrowed and modified from the public domain one in the MinGW toolchain. Also, Paul Hsieh has a portable one with a BSD license:  <a href="http://www.azillionmonkeys.com/qed/pstdint.h" rel="nofollow">http://www.azillionmonkeys.com/qed/pstdint.h</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gordon Brandly</title>
		<link>http://embeddedgurus.com/barr-code/2009/03/coding-standard-rule-6-use-c99s-fixed-width-integer-type-names/comment-page-1/#comment-43</link>
		<dc:creator>Gordon Brandly</dc:creator>
		<pubDate>Tue, 31 Mar 2009 20:03:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfcdev.org/test-stack/2009/03/31/coding-standard-rule-6-use-c99s-fixed-width-integer-type-names/#comment-43</guid>
		<description>Oops. Gotta watch those angle brackets when you&#039;re writing for the Web. :)Anyway, even though your reference to &quot;stdint.h&quot; got swallowed, I must agree: to me it&#039;s by far the most useful feature of the C99 standard. I created my own version of that header for the C compiler I use for my Microchip work (Knudsen), and in my C++ code I use the Boost &quot;boost/cstdint.hpp&quot; library for the C++ compilers that don&#039;t already have a stdint.h.It&#039;s one less chance for confusion when I switch among the three or four different compilers I use regularly!</description>
		<content:encoded><![CDATA[<p>Oops. Gotta watch those angle brackets when you&#8217;re writing for the Web. <img src='http://embeddedgurus.com/barr-code/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> Anyway, even though your reference to &#8220;stdint.h&#8221; got swallowed, I must agree: to me it&#8217;s by far the most useful feature of the C99 standard. I created my own version of that header for the C compiler I use for my Microchip work (Knudsen), and in my C++ code I use the Boost &#8220;boost/cstdint.hpp&#8221; library for the C++ compilers that don&#8217;t already have a stdint.h.It&#8217;s one less chance for confusion when I switch among the three or four different compilers I use regularly!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

