<?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"
	>
<channel>
	<title>Comments on: Undocumented Changes in Java 6 Mustang: IOError</title>
	<atom:link href="http://cafe.elharo.com/blogroll/undocumented-changes-in-java-6-mustang-ioerror/feed/" rel="self" type="application/rss+xml" />
	<link>http://cafe.elharo.com/blogroll/undocumented-changes-in-java-6-mustang-ioerror/</link>
	<description>Longer than a blog; shorter than a book</description>
	<pubDate>Tue, 06 Jan 2009 12:38:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Dr Aaron Kans</title>
		<link>http://cafe.elharo.com/blogroll/undocumented-changes-in-java-6-mustang-ioerror/#comment-325492</link>
		<dc:creator>Dr Aaron Kans</dc:creator>
		<pubDate>Tue, 16 Dec 2008 12:30:57 +0000</pubDate>
		<guid isPermaLink="false">http://minicafe.elharo.com/uncategorized/undocumented-changes-in-java-6-mustang-ioerror/#comment-325492</guid>
		<description>IOError seems to be an unchecked excpetion, whereas IOException was checked.

Is this why it was developed? To change from a rigorous checked excpetion to a looser unchecked exception for IO errors? If so is this not a dangerous thing to do? Surely all IO errors chould be checked?</description>
		<content:encoded><![CDATA[<p>IOError seems to be an unchecked excpetion, whereas IOException was checked.</p>
<p>Is this why it was developed? To change from a rigorous checked excpetion to a looser unchecked exception for IO errors? If so is this not a dangerous thing to do? Surely all IO errors chould be checked?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Texas Hold Em Tournament Rule</title>
		<link>http://cafe.elharo.com/blogroll/undocumented-changes-in-java-6-mustang-ioerror/#comment-84198</link>
		<dc:creator>Texas Hold Em Tournament Rule</dc:creator>
		<pubDate>Sun, 29 Apr 2007 18:39:07 +0000</pubDate>
		<guid isPermaLink="false">http://minicafe.elharo.com/uncategorized/undocumented-changes-in-java-6-mustang-ioerror/#comment-84198</guid>
		<description>&lt;strong&gt;Texas Hold Em Tournament Rule&lt;/strong&gt;

portend?armpits milliwatt rangeland </description>
		<content:encoded><![CDATA[<p><strong>Texas Hold Em Tournament Rule</strong></p>
<p>portend?armpits milliwatt rangeland</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elliotte Rusty Harold</title>
		<link>http://cafe.elharo.com/blogroll/undocumented-changes-in-java-6-mustang-ioerror/#comment-161</link>
		<dc:creator>Elliotte Rusty Harold</dc:creator>
		<pubDate>Thu, 02 Feb 2006 20:54:03 +0000</pubDate>
		<guid isPermaLink="false">http://minicafe.elharo.com/uncategorized/undocumented-changes-in-java-6-mustang-ioerror/#comment-161</guid>
		<description>What would such a situation be? What methods might throw this error?</description>
		<content:encoded><![CDATA[<p>What would such a situation be? What methods might throw this error?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Reinhold</title>
		<link>http://cafe.elharo.com/blogroll/undocumented-changes-in-java-6-mustang-ioerror/#comment-160</link>
		<dc:creator>Mark Reinhold</dc:creator>
		<pubDate>Thu, 02 Feb 2006 20:51:24 +0000</pubDate>
		<guid isPermaLink="false">http://minicafe.elharo.com/uncategorized/undocumented-changes-in-java-6-mustang-ioerror/#comment-160</guid>
		<description>The new IOError class was defined in combination with the
new java.io.Console class.  It's for use in situations where
an unrecoverable I/O error occurs and the most appropriate
response is to terminate the program rather than attempt to
handle the exception.

The IOError class, along with many other enhancements, will
be documented in the forthcoming Mustang maintenance review
in the JCP.</description>
		<content:encoded><![CDATA[<p>The new IOError class was defined in combination with the<br />
new java.io.Console class.  It&#8217;s for use in situations where<br />
an unrecoverable I/O error occurs and the most appropriate<br />
response is to terminate the program rather than attempt to<br />
handle the exception.</p>
<p>The IOError class, along with many other enhancements, will<br />
be documented in the forthcoming Mustang maintenance review<br />
in the JCP.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
