<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: C++ Software Design Tips Guidelines Checklist</title>
	<link>http://www.prashantmhatre.com/programming/c-software-design-tips-guidelines-checklist/</link>
	<description>Make Money, Programming, Bollywood, Marathi</description>
	<pubDate>Sat, 22 Nov 2008 13:07:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>By: C++ Software Design Tips Guidelines Checklist</title>
		<link>http://www.prashantmhatre.com/programming/c-software-design-tips-guidelines-checklist/#comment-21</link>
		<dc:creator>C++ Software Design Tips Guidelines Checklist</dc:creator>
		<pubDate>Sun, 09 Mar 2008 03:37:39 +0000</pubDate>
		<guid>http://www.prashantmhatre.com/programming/c-software-design-tips-guidelines-checklist/#comment-21</guid>
		<description>[...] AhTim wrote an interesting post today onHere&#8217;s a quick excerptC++ Software Design Tips Guidelines Checklist * Open/close principle * Prefer free to member functions * Consider moving private members to the implementation file– pimpl idiom (handle/body, compilation firewall) * Namespace names after &#8230; [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] AhTim wrote an interesting post today onHere&#8217;s a quick excerptC++ Software Design Tips Guidelines Checklist * Open/close principle * Prefer free to member functions * Consider moving private members to the implementation file– pimpl idiom (handle/body, compilation firewall) * Namespace names after &#8230; [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
