<?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/"
	>

<channel>
	<title>Down Home Country Coding With Scott Selikoff and Jeanne Boyarsky &#187; null</title>
	<atom:link href="http://www.selikoff.net/tag/null/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.selikoff.net</link>
	<description>Java/J2EE Software Development and Technology Discussion Blog</description>
	<lastBuildDate>Mon, 30 Jan 2012 02:27:13 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Never return Null Arrays!</title>
		<link>http://www.selikoff.net/2008/10/15/never-return-null-arrays/</link>
		<comments>http://www.selikoff.net/2008/10/15/never-return-null-arrays/#comments</comments>
		<pubDate>Wed, 15 Oct 2008 06:03:23 +0000</pubDate>
		<dc:creator>Scott Selikoff</dc:creator>
				<category><![CDATA[Development Process]]></category>
		<category><![CDATA[array]]></category>
		<category><![CDATA[Java/J2EE]]></category>
		<category><![CDATA[null]]></category>
		<category><![CDATA[NullPointerException]]></category>

		<guid isPermaLink="false">http://www.selikoff.net/blog/?p=569</guid>
		<description><![CDATA[Continuing on Jeanne&#8217;s theme of nulls, its a pet peeve of mine when I come across code that returns null arrays instead of empty arrays. The purpose of this post is to discuss some of the reasons why its a good practice to return empty arrays over null arrays, including Collection objects or typed array. [...]]]></description>
		<wfw:commentRss>http://www.selikoff.net/2008/10/15/never-return-null-arrays/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>null checking in the extreme</title>
		<link>http://www.selikoff.net/2008/10/13/null-checking-in-the-extreme/</link>
		<comments>http://www.selikoff.net/2008/10/13/null-checking-in-the-extreme/#comments</comments>
		<pubDate>Mon, 13 Oct 2008 18:23:07 +0000</pubDate>
		<dc:creator>Jeanne Boyarsky</dc:creator>
				<category><![CDATA[Development Process]]></category>
		<category><![CDATA[Java/J2EE]]></category>
		<category><![CDATA[null]]></category>

		<guid isPermaLink="false">http://www.selikoff.net/blog/?p=309</guid>
		<description><![CDATA[In Java, we&#8217;re told to check for nulls to avoid unexpected null pointer exceptions.  This can be taken too far though.  Consider the following code: When did builder have the opportunity to become null? By definition, a constructor creates an object. We just called the constructor. We know builder isn&#8217;t null. Having extra code around [...]]]></description>
		<wfw:commentRss>http://www.selikoff.net/2008/10/13/null-checking-in-the-extreme/feed/</wfw:commentRss>
		<slash:comments>17</slash:comments>
		</item>
	</channel>
</rss>

