<?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 Best Practices for C – Part – 2</title>
	<atom:link href="http://www.ajatus.in/2009/10/coding-best-practices-for-c-part-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ajatus.in/2009/10/coding-best-practices-for-c-part-2/</link>
	<description>The Ajatus Software Website</description>
	<lastBuildDate>Wed, 08 Sep 2010 12:36:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Mulch Newark</title>
		<link>http://www.ajatus.in/2009/10/coding-best-practices-for-c-part-2/comment-page-1/#comment-318</link>
		<dc:creator>Mulch Newark</dc:creator>
		<pubDate>Sun, 14 Mar 2010 05:50:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.ajatus.in/?p=235#comment-318</guid>
		<description>Thanks a  lot for this, I  am greatful for the info</description>
		<content:encoded><![CDATA[<p>Thanks a  lot for this, I  am greatful for the info</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shamwow Vince</title>
		<link>http://www.ajatus.in/2009/10/coding-best-practices-for-c-part-2/comment-page-1/#comment-305</link>
		<dc:creator>Shamwow Vince</dc:creator>
		<pubDate>Sun, 07 Mar 2010 00:07:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.ajatus.in/?p=235#comment-305</guid>
		<description>hey there.. great info, I didn&#039;t think I would find exactly what I was looking for until I came across this site on google!</description>
		<content:encoded><![CDATA[<p>hey there.. great info, I didn&#8217;t think I would find exactly what I was looking for until I came across this site on google!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Internet Banking</title>
		<link>http://www.ajatus.in/2009/10/coding-best-practices-for-c-part-2/comment-page-1/#comment-292</link>
		<dc:creator>Internet Banking</dc:creator>
		<pubDate>Thu, 04 Feb 2010 06:53:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.ajatus.in/?p=235#comment-292</guid>
		<description>I think that is an interesting point, it made me think a bit.  Thanks for sparking my thinking cap.  Sometimes I get so much in a rut that I just feel like a record.</description>
		<content:encoded><![CDATA[<p>I think that is an interesting point, it made me think a bit.  Thanks for sparking my thinking cap.  Sometimes I get so much in a rut that I just feel like a record.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mini games</title>
		<link>http://www.ajatus.in/2009/10/coding-best-practices-for-c-part-2/comment-page-1/#comment-244</link>
		<dc:creator>mini games</dc:creator>
		<pubDate>Tue, 10 Nov 2009 10:46:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.ajatus.in/?p=235#comment-244</guid>
		<description>Hi webmaster, wonderful article. Pleasee continue this great work!!!!</description>
		<content:encoded><![CDATA[<p>Hi webmaster, wonderful article. Pleasee continue this great work!!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph Poirier</title>
		<link>http://www.ajatus.in/2009/10/coding-best-practices-for-c-part-2/comment-page-1/#comment-82</link>
		<dc:creator>Joseph Poirier</dc:creator>
		<pubDate>Mon, 19 Oct 2009 06:38:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.ajatus.in/?p=235#comment-82</guid>
		<description>Hi,
Concerning bullet 11 in the &quot;STANDARDS&quot; section above. The asterisk isn&#039;t a type qualifier, like for example const and volatile, but rather a type specifier. And I disagree with where the asterisk _should_ be placed. Common convention is to place the asterisk with the variable name, but that always seemed strange to me since it&#039;s the combining of the primitive type with the asterisk that creates the pointer type. To my crazy brain, separating the asterisk from the primitive type is no different from pulling the &#039;r&#039; off the end of &#039;char&#039; and pre-pending it to the variable being defined. Yeah, sounds crazy... Also, IMHO, defining multiple (uninitialized) variables on the same line is bad practice. The argument for saving screen real estate these days is debatable. Fortunately, the company I work for feels the same way as myself and it&#039;s not allowed.</description>
		<content:encoded><![CDATA[<p>Hi,<br />
Concerning bullet 11 in the &#8220;STANDARDS&#8221; section above. The asterisk isn&#8217;t a type qualifier, like for example const and volatile, but rather a type specifier. And I disagree with where the asterisk _should_ be placed. Common convention is to place the asterisk with the variable name, but that always seemed strange to me since it&#8217;s the combining of the primitive type with the asterisk that creates the pointer type. To my crazy brain, separating the asterisk from the primitive type is no different from pulling the &#8216;r&#8217; off the end of &#8216;char&#8217; and pre-pending it to the variable being defined. Yeah, sounds crazy&#8230; Also, IMHO, defining multiple (uninitialized) variables on the same line is bad practice. The argument for saving screen real estate these days is debatable. Fortunately, the company I work for feels the same way as myself and it&#8217;s not allowed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anup</title>
		<link>http://www.ajatus.in/2009/10/coding-best-practices-for-c-part-2/comment-page-1/#comment-20</link>
		<dc:creator>Anup</dc:creator>
		<pubDate>Wed, 14 Oct 2009 04:29:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.ajatus.in/?p=235#comment-20</guid>
		<description>Hi Debesh,
NIce article.I hope this article is as much useful for starters as it is for avid coders like you.
One suggestion: it would be helpful if you can give a sample program which has been coded as per the BEST PRACTICES.Then explain ur best practices tips by pointing to that part of code which you  want to explain.From my experience, a digramatic representation lives long in the memory and is easier to understand than just a theoritical summary.
P.S: A sugestion only meant for understanding of laymans like me.Not for developers like you.</description>
		<content:encoded><![CDATA[<p>Hi Debesh,<br />
NIce article.I hope this article is as much useful for starters as it is for avid coders like you.<br />
One suggestion: it would be helpful if you can give a sample program which has been coded as per the BEST PRACTICES.Then explain ur best practices tips by pointing to that part of code which you  want to explain.From my experience, a digramatic representation lives long in the memory and is easier to understand than just a theoritical summary.<br />
P.S: A sugestion only meant for understanding of laymans like me.Not for developers like you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
