<?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: Ten Little Soul Crushing Features of Java</title>
	<atom:link href="http://blog.darevay.com/2009/04/ten-little-soul-crushing-features-of-java/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.darevay.com/2009/04/ten-little-soul-crushing-features-of-java/</link>
	<description>You know, software and some other stuff like maybe guitar or something</description>
	<lastBuildDate>Tue, 15 Jun 2010 15:31:37 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dario</title>
		<link>http://blog.darevay.com/2009/04/ten-little-soul-crushing-features-of-java/comment-page-1/#comment-1837</link>
		<dc:creator>Dario</dc:creator>
		<pubDate>Wed, 22 Jul 2009 15:43:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.darevay.com/?p=205#comment-1837</guid>
		<description>IllegalArgumentException is to be thrown when argument is illegal or inappropiate, and it&#039;s a RuntimeException (About RuntimeException, since every method can throw it, none is required to tell, so it&#039;s easy to miss that or any of its subclasses)
MalformedURLException is more strict, specifically it hasn&#039;t a recognizable protocol or the url string couldn&#039;t be parsed. It&#039;s a IOException subclass, no a RuntimeException one, so it has to be declared and thus it won&#039;t jump by surprise.
Beside RuntimeException family (like NullPointer, ClassCast, IndexOutOfBounds...), MalformedURLException seems full of sense to me...</description>
		<content:encoded><![CDATA[<p>IllegalArgumentException is to be thrown when argument is illegal or inappropiate, and it&#8217;s a RuntimeException (About RuntimeException, since every method can throw it, none is required to tell, so it&#8217;s easy to miss that or any of its subclasses)<br />
MalformedURLException is more strict, specifically it hasn&#8217;t a recognizable protocol or the url string couldn&#8217;t be parsed. It&#8217;s a IOException subclass, no a RuntimeException one, so it has to be declared and thus it won&#8217;t jump by surprise.<br />
Beside RuntimeException family (like NullPointer, ClassCast, IndexOutOfBounds&#8230;), MalformedURLException seems full of sense to me&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dave</title>
		<link>http://blog.darevay.com/2009/04/ten-little-soul-crushing-features-of-java/comment-page-1/#comment-1642</link>
		<dc:creator>dave</dc:creator>
		<pubDate>Fri, 08 May 2009 17:31:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.darevay.com/?p=205#comment-1642</guid>
		<description>&lt;a href=&quot;#comment-1641&quot; rel=&quot;nofollow&quot;&gt;@Svend&lt;/a&gt; 
join() can be implemented with concat(), but they&#039;re not the same. I want to write:
&quot;, &quot;.join(Arrays.asList(&quot;Jim&quot;, &quot;Bob&quot;, &quot;Al&quot;));
and get:
&quot;Jim, Bob, Al&quot;.

You&#039;re code for reading a file is fine, but, again it&#039;s a matter of convenience. Rather than writing that function over and over from project to project I want it built in:
String s = String.fromFile(&quot;test.txt&quot;);
or something like that.

I&#039;ve just been spoiled by scripting languages I guess.</description>
		<content:encoded><![CDATA[<p><a href="#comment-1641" rel="nofollow">@Svend</a><br />
join() can be implemented with concat(), but they&#8217;re not the same. I want to write:<br />
&#8220;, &#8220;.join(Arrays.asList(&#8220;Jim&#8221;, &#8220;Bob&#8221;, &#8220;Al&#8221;));<br />
and get:<br />
&#8220;Jim, Bob, Al&#8221;.</p>
<p>You&#8217;re code for reading a file is fine, but, again it&#8217;s a matter of convenience. Rather than writing that function over and over from project to project I want it built in:<br />
String s = String.fromFile(&#8220;test.txt&#8221;);<br />
or something like that.</p>
<p>I&#8217;ve just been spoiled by scripting languages I guess.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Svend</title>
		<link>http://blog.darevay.com/2009/04/ten-little-soul-crushing-features-of-java/comment-page-1/#comment-1641</link>
		<dc:creator>Svend</dc:creator>
		<pubDate>Fri, 08 May 2009 17:22:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.darevay.com/?p=205#comment-1641</guid>
		<description>1. Isn&#039;t that what String.concat(String) is for?
10. InputStream and Reader are streaming interfaces, which means that they can have more content than you can fit in an array. It sounds like you&#039;re talking about file based input stream or readers, in which case you can do this (provided your file length is smaller than 2GB):
method(File file) {
  FileInputStream fis = new FileInputStream(file);
  byte[] bytes = new byte[(int)file.length());
  fis.read(bytes);
}</description>
		<content:encoded><![CDATA[<p>1. Isn&#8217;t that what String.concat(String) is for?<br />
10. InputStream and Reader are streaming interfaces, which means that they can have more content than you can fit in an array. It sounds like you&#8217;re talking about file based input stream or readers, in which case you can do this (provided your file length is smaller than 2GB):<br />
method(File file) {<br />
  FileInputStream fis = new FileInputStream(file);<br />
  byte[] bytes = new byte[(int)file.length());<br />
  fis.read(bytes);<br />
}</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dave</title>
		<link>http://blog.darevay.com/2009/04/ten-little-soul-crushing-features-of-java/comment-page-1/#comment-1162</link>
		<dc:creator>dave</dc:creator>
		<pubDate>Sun, 19 Apr 2009 12:09:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.darevay.com/?p=205#comment-1162</guid>
		<description>Yep. It&#039;s fixed now. Thanks for catching that.</description>
		<content:encoded><![CDATA[<p>Yep. It&#8217;s fixed now. Thanks for catching that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mkneissl</title>
		<link>http://blog.darevay.com/2009/04/ten-little-soul-crushing-features-of-java/comment-page-1/#comment-1159</link>
		<dc:creator>mkneissl</dc:creator>
		<pubDate>Sun, 19 Apr 2009 11:51:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.darevay.com/?p=205#comment-1159</guid>
		<description>Mostly agree to your list, but shouldn&#039;t 6) read &quot;non-empty directory&quot;?</description>
		<content:encoded><![CDATA[<p>Mostly agree to your list, but shouldn&#8217;t 6) read &#8220;non-empty directory&#8221;?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: oldmicah</title>
		<link>http://blog.darevay.com/2009/04/ten-little-soul-crushing-features-of-java/comment-page-1/#comment-818</link>
		<dc:creator>oldmicah</dc:creator>
		<pubDate>Thu, 09 Apr 2009 16:00:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.darevay.com/?p=205#comment-818</guid>
		<description>Pretty amazing list, although a perhaps a little exaggerated.   I have only found myself cussing late at night over #2,3,4,6,78,9, and 10.</description>
		<content:encoded><![CDATA[<p>Pretty amazing list, although a perhaps a little exaggerated.   I have only found myself cussing late at night over #2,3,4,6,78,9, and 10.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
