<?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: Checked Exceptions are Waste</title>
	<atom:link href="http://andypalmer.com/2008/09/checked-exceptions/feed/" rel="self" type="application/rss+xml" />
	<link>http://andypalmer.com/2008/09/checked-exceptions/</link>
	<description>Views on software, technology, consulting and business process</description>
	<lastBuildDate>Fri, 18 Nov 2011 07:13:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Kevin Wong</title>
		<link>http://andypalmer.com/2008/09/checked-exceptions/comment-page-1/#comment-1062</link>
		<dc:creator>Kevin Wong</dc:creator>
		<pubDate>Mon, 21 Sep 2009 10:23:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.andypalmer.com/blog/?p=13#comment-1062</guid>
		<description>I always change my Eclipse default catch clause to:&lt;br&gt;    throw new RuntimeException(e);&lt;br&gt;&lt;br&gt;Don&#039;t add and exception to the throws clause unless it will make sense to the caller.  If it&#039;s a case that should never happen, or cannot be handled, wrap it in a RuntimeException, which effectively converts the checked exception to an unchecked one.&lt;br&gt;&lt;br&gt;I don&#039;t see why an &quot;ignores&quot; clause couldn&#039;t be added to Java methods to do this wrapping automatically.</description>
		<content:encoded><![CDATA[<p>I always change my Eclipse default catch clause to:<br />    throw new RuntimeException(e);</p>
<p>Don&#39;t add and exception to the throws clause unless it will make sense to the caller.  If it&#39;s a case that should never happen, or cannot be handled, wrap it in a RuntimeException, which effectively converts the checked exception to an unchecked one.</p>
<p>I don&#39;t see why an &#8220;ignores&#8221; clause couldn&#39;t be added to Java methods to do this wrapping automatically.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Palmer &#187; Installing Eclipse</title>
		<link>http://andypalmer.com/2008/09/checked-exceptions/comment-page-1/#comment-128</link>
		<dc:creator>Andy Palmer &#187; Installing Eclipse</dc:creator>
		<pubDate>Sun, 22 Feb 2009 23:11:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.andypalmer.com/blog/?p=13#comment-128</guid>
		<description>[...] also discussed my thoughts on checked exceptions. I prefer to not silently hide the exception with a stack trace, I also don&#8217;t want to make my [...]</description>
		<content:encoded><![CDATA[<p>[...] also discussed my thoughts on checked exceptions. I prefer to not silently hide the exception with a stack trace, I also don&#8217;t want to make my [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Freeman</title>
		<link>http://andypalmer.com/2008/09/checked-exceptions/comment-page-1/#comment-26</link>
		<dc:creator>Steve Freeman</dc:creator>
		<pubDate>Sun, 09 Nov 2008 18:25:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.andypalmer.com/blog/?p=13#comment-26</guid>
		<description>The reason Java checked exceptions are a pain is because, like everything in Java, they didn&#039;t quite finish when they adopted the idea. In Modula-3, there is a FATAL pragma which meant that you can declare that you don&#039;t know how to handle a checked exception within a given scope. If such an exception occurs then the program fails. It&#039;s so simple  but it makes all the difference to the usability of checked exceptions.

The point of checked exceptions is that it allows me to know all the paths out of a chunk of code, otherwise I have to assume that any method call can fail and over-protect the logic.</description>
		<content:encoded><![CDATA[<p>The reason Java checked exceptions are a pain is because, like everything in Java, they didn&#8217;t quite finish when they adopted the idea. In Modula-3, there is a FATAL pragma which meant that you can declare that you don&#8217;t know how to handle a checked exception within a given scope. If such an exception occurs then the program fails. It&#8217;s so simple  but it makes all the difference to the usability of checked exceptions.</p>
<p>The point of checked exceptions is that it allows me to know all the paths out of a chunk of code, otherwise I have to assume that any method call can fail and over-protect the logic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rugbyhead</title>
		<link>http://andypalmer.com/2008/09/checked-exceptions/comment-page-1/#comment-21</link>
		<dc:creator>Rugbyhead</dc:creator>
		<pubDate>Sat, 06 Sep 2008 17:27:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.andypalmer.com/blog/?p=13#comment-21</guid>
		<description>Liking the ExceptionHandler object idea, could prove to be very versatile and flexible...&lt;br/&gt;Next workshop?? :D</description>
		<content:encoded><![CDATA[<p>Liking the ExceptionHandler object idea, could prove to be very versatile and flexible&#8230;<br />Next workshop?? <img src='http://andypalmer.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

