<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>cplusplus.co.il &#187; design</title>
	<atom:link href="http://cplusplus.co.il/category/cpp/design/feed/" rel="self" type="application/rss+xml" />
	<link>http://cplusplus.co.il</link>
	<description>Discussing modern C++ and related topics.</description>
	<lastBuildDate>Tue, 31 Jan 2012 18:28:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
<cloud domain='cplusplus.co.il' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://s2.wp.com/i/buttonw-com.png</url>
		<title>cplusplus.co.il &#187; design</title>
		<link>http://cplusplus.co.il</link>
	</image>
	<atom:link rel="search" type="application/opensearchdescription+xml" href="http://cplusplus.co.il/osd.xml" title="cplusplus.co.il" />
	<atom:link rel='hub' href='http://cplusplus.co.il/?pushpress=hub'/>
		<item>
		<title>Using the state design pattern to implement FSMs</title>
		<link>http://cplusplus.co.il/2009/11/13/using-the-state-design-pattern-to-implement-fsms/</link>
		<comments>http://cplusplus.co.il/2009/11/13/using-the-state-design-pattern-to-implement-fsms/#comments</comments>
		<pubDate>Fri, 13 Nov 2009 12:00:36 +0000</pubDate>
		<dc:creator>rmn</dc:creator>
				<category><![CDATA[design]]></category>

		<guid isPermaLink="false">http://cplusplus.co.il/?p=579</guid>
		<description><![CDATA[The State design pattern is a very useful design pattern. In this article we will exploit it to provide a very slick and elegant implementation of a Finite State Machine (FSM). First of all, a FSM consists of a finitie number of states and a predefined set of rules defining the transitions between all these states. Each [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=cplusplus.co.il&amp;blog=8968104&amp;post=579&amp;subd=cpptalk&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://cplusplus.co.il/2009/11/13/using-the-state-design-pattern-to-implement-fsms/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
	
		<media:content url="http://0.gravatar.com/avatar/4ceb7c3e96e1e6c9fbef377af219fc0a?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">rmn</media:title>
		</media:content>
	</item>
		<item>
		<title>Designing for testability: factories</title>
		<link>http://cplusplus.co.il/2009/09/18/designing-for-testability-through-factories/</link>
		<comments>http://cplusplus.co.il/2009/09/18/designing-for-testability-through-factories/#comments</comments>
		<pubDate>Fri, 18 Sep 2009 13:03:58 +0000</pubDate>
		<dc:creator>rmn</dc:creator>
				<category><![CDATA[design]]></category>

		<guid isPermaLink="false">http://cpptalk.wordpress.com/?p=233</guid>
		<description><![CDATA[When we approach the process of designing our software, there are many issues we must address in order to be succesful. One of these issues (and you are free to disagree) is: How will we be able to test (or debug) our hand crafted piece of code? This post will attempt to at least provide [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=cplusplus.co.il&amp;blog=8968104&amp;post=233&amp;subd=cpptalk&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://cplusplus.co.il/2009/09/18/designing-for-testability-through-factories/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
	
		<media:content url="http://0.gravatar.com/avatar/4ceb7c3e96e1e6c9fbef377af219fc0a?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">rmn</media:title>
		</media:content>
	</item>
		<item>
		<title>Final/frozen classes in c++</title>
		<link>http://cplusplus.co.il/2009/09/01/final-frozen-classes-in-cpp/</link>
		<comments>http://cplusplus.co.il/2009/09/01/final-frozen-classes-in-cpp/#comments</comments>
		<pubDate>Tue, 01 Sep 2009 18:38:22 +0000</pubDate>
		<dc:creator>rmn</dc:creator>
				<category><![CDATA[design]]></category>

		<guid isPermaLink="false">http://cpptalk.wordpress.com/?p=88</guid>
		<description><![CDATA[A final (or frozen) class is a class that can&#8217;t be further extended by inheritance. In many languages we have different keywords for such behaviour, such as &#8220;final&#8221; in Java, or &#8220;sealed&#8221; in c#. Unfortunetly we don&#8217;t have such construct in c++; but we can use other mechanisms to easily achieve this goal. As i&#8217;ve mentioned [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=cplusplus.co.il&amp;blog=8968104&amp;post=88&amp;subd=cpptalk&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://cplusplus.co.il/2009/09/01/final-frozen-classes-in-cpp/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
	
		<media:content url="http://0.gravatar.com/avatar/4ceb7c3e96e1e6c9fbef377af219fc0a?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">rmn</media:title>
		</media:content>
	</item>
		<item>
		<title>Pure virtual destructor</title>
		<link>http://cplusplus.co.il/2009/08/22/pure-virtual-destructor/</link>
		<comments>http://cplusplus.co.il/2009/08/22/pure-virtual-destructor/#comments</comments>
		<pubDate>Fri, 21 Aug 2009 22:13:38 +0000</pubDate>
		<dc:creator>rmn</dc:creator>
				<category><![CDATA[design]]></category>

		<guid isPermaLink="false">http://cpptalk.wordpress.com/?p=56</guid>
		<description><![CDATA[Sometimes you would like to create an abstract class, but there is no method you could naturally declare as pure virtual (=0) in order to achieve that (in a tag interface, for example). In such cases the destructor may be the perfect candidate: as it should always be declared virtual if inheritance is considered, it may as well [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=cplusplus.co.il&amp;blog=8968104&amp;post=56&amp;subd=cpptalk&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://cplusplus.co.il/2009/08/22/pure-virtual-destructor/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
	
		<media:content url="http://0.gravatar.com/avatar/4ceb7c3e96e1e6c9fbef377af219fc0a?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">rmn</media:title>
		</media:content>
	</item>
	</channel>
</rss>
