<?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: Shouldn&#8217;t RAII should be RDID???</title>
	<atom:link href="http://www.somethingorothersoft.com/2009/12/11/shouldnt-raii-should-be-rdid/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.somethingorothersoft.com/2009/12/11/shouldnt-raii-should-be-rdid/</link>
	<description>About Software Development And Other Stuff By Igor Zevaka</description>
	<lastBuildDate>Wed, 28 Jul 2010 12:50:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: rmn</title>
		<link>http://www.somethingorothersoft.com/2009/12/11/shouldnt-raii-should-be-rdid/comment-page-1/#comment-242</link>
		<dc:creator>rmn</dc:creator>
		<pubDate>Tue, 05 Jan 2010 13:30:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.somethingorothersoft.com/?p=157#comment-242</guid>
		<description>&lt;p&gt;I couldn&#039;t agree more about what you said on design patterns :) I think that the fact that the design patterns only give a name to something most of us have been doing anyway, is just great - it makes it easier to discuss such practices and formalize the design decisions we make. It basically provides us with a proper terminology.&lt;/p&gt;

&lt;p&gt;Regarding RAII.. Well, perhaps you are right :) The most important aspect of it is indeed the fact that the destructor is guaranteed to work, no matter what happens - be it a rogue exception, regular termination of the code block, anything.&lt;/p&gt;

&lt;p&gt;Thanks for the read.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I couldn&#8217;t agree more about what you said on design patterns :) I think that the fact that the design patterns only give a name to something most of us have been doing anyway, is just great &#8211; it makes it easier to discuss such practices and formalize the design decisions we make. It basically provides us with a proper terminology.</p>

<p>Regarding RAII.. Well, perhaps you are right :) The most important aspect of it is indeed the fact that the destructor is guaranteed to work, no matter what happens &#8211; be it a rogue exception, regular termination of the code block, anything.</p>

<p>Thanks for the read.</p>]]></content:encoded>
	</item>
</channel>
</rss>
