<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.newlc.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>NewLC - When Symbian met Design Patterns (1) -- State Pattern - Comments</title>
 <link>http://www.newlc.com/en/when-symbian-met-design-patterns-1-state-pattern</link>
 <description>Comments for &quot;When Symbian met Design Patterns (1) -- State Pattern&quot;</description>
 <language>en</language>
<item>
 <title>When Symbian met Design Patterns (1) -- State Pattern</title>
 <link>http://www.newlc.com/en/when-symbian-met-design-patterns-1-state-pattern</link>
 <description>&lt;p&gt;Almost every software has state machines, It&#039;s one of those basic elements of the program. Different states of an object corresponding to different behaviors of it. The simplest state machine is likely the combination of if/else statements or switch/case statements within one class. It works! Absolutely! But what if we have 10 &quot;if&quot; and 10 &quot;else&quot;? Let&#039;s see what could the State Pattern do for us?&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://www.newlc.com/en/when-symbian-met-design-patterns-1-state-pattern&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.newlc.com/en/when-symbian-met-design-patterns-1-state-pattern#comments</comments>
 <category domain="http://www.newlc.com/en/taxonomy/term/1">Basics</category>
 <category domain="http://www.newlc.com/en/taxonomy/term/41">Symbian OS</category>
 <category domain="http://www.newlc.com/en/taxonomy/term/42">UIQ</category>
 <category domain="http://www.newlc.com/en/taxonomy/term/162">Design Pattern</category>
 <pubDate>Tue, 24 Apr 2007 16:35:10 +0200</pubDate>
 <dc:creator>rensijie</dc:creator>
 <guid isPermaLink="false">1078 at http://www.newlc.com</guid>
</item>
</channel>
</rss>
