<?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>Reacties op: Java best practices 2 &#8211; Explicit cases</title>
	<atom:link href="http://jdevelopment.nl/java/java-best-practices-2-explicit-cases/feed/" rel="self" type="application/rss+xml" />
	<link>http://jdevelopment.nl/java/java-best-practices-2-explicit-cases/</link>
	<description>designing a new generation of software</description>
	<lastBuildDate>Wed, 10 Mar 2010 23:29:38 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Door: developer</title>
		<link>http://jdevelopment.nl/java/java-best-practices-2-explicit-cases/comment-page-1/#comment-15</link>
		<dc:creator>developer</dc:creator>
		<pubDate>Thu, 16 Aug 2007 06:00:32 +0000</pubDate>
		<guid isPermaLink="false">http://jdevelopment.nl/java/java-best-practices-2-explicit-cases/#comment-15</guid>
		<description>I have the same experiences that Exlpilit cases can&#160; not only make the program more readable but also more expandable. It&#039;s also a good practice to give the cases&#160; logical names.</description>
		<content:encoded><![CDATA[<p>I have the same experiences that Exlpilit cases can&nbsp; not only make the program more readable but also more expandable. It&#8217;s also a good practice to give the cases&nbsp; logical names.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
