<?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 for spiros.blog()</title>
	<atom:link href="http://www.tzavellas.com/techblog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tzavellas.com/techblog</link>
	<description>Spiros Tzavellas’s blog, mostly on software development and Java.</description>
	<lastBuildDate>Tue, 28 Sep 2010 18:21:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>Comment on Catching Throwable in Scala by spiros</title>
		<link>http://www.tzavellas.com/techblog/2010/09/20/catching-throwable-in-scala/comment-page-1/#comment-219</link>
		<dc:creator>spiros</dc:creator>
		<pubDate>Tue, 28 Sep 2010 18:21:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.tzavellas.com/techblog/?p=427#comment-219</guid>
		<description>The article that @inca mentioned can be found at http://incarnate.ru/post/1198942448/scala-runtime-nonlocalreturncontrol</description>
		<content:encoded><![CDATA[<p>The article that @inca mentioned can be found at <a href="http://incarnate.ru/post/1198942448/scala-runtime-nonlocalreturncontrol" rel="nofollow">http://incarnate.ru/post/1198942448/scala-runtime-nonlocalreturncontrol</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Catching Throwable in Scala by spiros</title>
		<link>http://www.tzavellas.com/techblog/2010/09/20/catching-throwable-in-scala/comment-page-1/#comment-218</link>
		<dc:creator>spiros</dc:creator>
		<pubDate>Tue, 28 Sep 2010 18:19:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.tzavellas.com/techblog/?p=427#comment-218</guid>
		<description>It is not a good idea to catch Throwable because java.lang.Error extends Throwable and a lot of Error classes (like ThreadDeath) almost always should never get caught. When you want to catch a Throwable or Error it is far better to catch only the specific type.

I agree with you that non-local returns should be avoided but I wouldn&#039;t want to completely eliminate them from my code.

BTW I really like Circumflex, keep up the good work!</description>
		<content:encoded><![CDATA[<p>It is not a good idea to catch Throwable because java.lang.Error extends Throwable and a lot of Error classes (like ThreadDeath) almost always should never get caught. When you want to catch a Throwable or Error it is far better to catch only the specific type.</p>
<p>I agree with you that non-local returns should be avoided but I wouldn&#8217;t want to completely eliminate them from my code.</p>
<p>BTW I really like Circumflex, keep up the good work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Catching Throwable in Scala by inca</title>
		<link>http://www.tzavellas.com/techblog/2010/09/20/catching-throwable-in-scala/comment-page-1/#comment-217</link>
		<dc:creator>inca</dc:creator>
		<pubDate>Tue, 28 Sep 2010 16:18:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.tzavellas.com/techblog/?p=427#comment-217</guid>
		<description>Wrote about the same. I think that `return` from within closures should be avoided, not really catching `Throwable`s.</description>
		<content:encoded><![CDATA[<p>Wrote about the same. I think that `return` from within closures should be avoided, not really catching `Throwable`s.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Catching Throwable in Scala by Amsayk</title>
		<link>http://www.tzavellas.com/techblog/2010/09/20/catching-throwable-in-scala/comment-page-1/#comment-212</link>
		<dc:creator>Amsayk</dc:creator>
		<pubDate>Sun, 26 Sep 2010 02:28:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.tzavellas.com/techblog/?p=427#comment-212</guid>
		<description>Thank you.</description>
		<content:encoded><![CDATA[<p>Thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Don&#8217;t use vars inside singleton objects by spiros</title>
		<link>http://www.tzavellas.com/techblog/2010/09/20/var-singleton-objects/comment-page-1/#comment-205</link>
		<dc:creator>spiros</dc:creator>
		<pubDate>Tue, 21 Sep 2010 05:55:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.tzavellas.com/techblog/?p=344#comment-205</guid>
		<description>I didn&#039;t knew that the mechanism with the static factory was optional. I really like Squeryl and I was really disappointed when I saw the vars inside SessionFactory. I should have kept reading the docs :-(

I believe that we both agree that the mechanism with the static factories has some serious drawbacks but it can be used in smaller apps as a convenience.

Thanks for letting me know! I&#039;ll update the article and  I&#039;ll probably give Squeryl a try really soon :-)</description>
		<content:encoded><![CDATA[<p>I didn&#8217;t knew that the mechanism with the static factory was optional. I really like Squeryl and I was really disappointed when I saw the vars inside SessionFactory. I should have kept reading the docs <img src='http://www.tzavellas.com/techblog/wp-includes/images/smilies/icon_sad.gif' alt=':-(' class='wp-smiley' /> </p>
<p>I believe that we both agree that the mechanism with the static factories has some serious drawbacks but it can be used in smaller apps as a convenience.</p>
<p>Thanks for letting me know! I&#8217;ll update the article and  I&#8217;ll probably give Squeryl a try really soon <img src='http://www.tzavellas.com/techblog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

