<?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 weblob.net</title>
	<atom:link href="http://www.weblob.net/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.weblob.net</link>
	<description>World WiSe Web</description>
	<lastBuildDate>Wed, 06 Jul 2011 22:06:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Comment on thx: error by Cauê Waneck</title>
		<link>http://www.weblob.net/2011/thx-error/#comment-66</link>
		<dc:creator>Cauê Waneck</dc:creator>
		<pubDate>Wed, 06 Jul 2011 22:06:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.weblob.net/?p=73#comment-66</guid>
		<description>Very nice post, Franco!

I like the way you handle error translations. My own preference for Errors, though, is to define them all as enums, so we can kind of strictly type all possible errors a library / code part can throw. When I&#039;m using them, sometimes I have a try with multiple different catches - one for each application part. The cool part about that is that you can add another error and get compilation errors if you forget to handle this type of error.</description>
		<content:encoded><![CDATA[<p>Very nice post, Franco!</p>
<p>I like the way you handle error translations. My own preference for Errors, though, is to define them all as enums, so we can kind of strictly type all possible errors a library / code part can throw. When I&#8217;m using them, sometimes I have a try with multiple different catches &#8211; one for each application part. The cool part about that is that you can add another error and get compilation errors if you forget to handle this type of error.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on thx: parsing dates by franco</title>
		<link>http://www.weblob.net/2011/thx-parsing-dates/#comment-65</link>
		<dc:creator>franco</dc:creator>
		<pubDate>Tue, 28 Jun 2011 16:06:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.weblob.net/?p=65#comment-65</guid>
		<description>No, there is not but that actually it is easier to implement than the parser ;)</description>
		<content:encoded><![CDATA[<p>No, there is not but that actually it is easier to implement than the parser <img src='http://www.weblob.net/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on thx: parsing dates by Ruben</title>
		<link>http://www.weblob.net/2011/thx-parsing-dates/#comment-64</link>
		<dc:creator>Ruben</dc:creator>
		<pubDate>Tue, 28 Jun 2011 16:01:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.weblob.net/?p=65#comment-64</guid>
		<description>Hee franco,

Nice work! It is also possible to use it the other way around?

Cheers!</description>
		<content:encoded><![CDATA[<p>Hee franco,</p>
<p>Nice work! It is also possible to use it the other way around?</p>
<p>Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on thx: basics by franco</title>
		<link>http://www.weblob.net/2011/thx-basics/#comment-63</link>
		<dc:creator>franco</dc:creator>
		<pubDate>Tue, 21 Jun 2011 13:42:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.weblob.net/?p=60#comment-63</guid>
		<description>Thank you, appreciated.</description>
		<content:encoded><![CDATA[<p>Thank you, appreciated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on thx: basics by Krzysztof Różalski</title>
		<link>http://www.weblob.net/2011/thx-basics/#comment-62</link>
		<dc:creator>Krzysztof Różalski</dc:creator>
		<pubDate>Tue, 21 Jun 2011 11:39:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.weblob.net/?p=60#comment-62</guid>
		<description>Great stuff Franco! For sure I need to put my hands on it :)</description>
		<content:encoded><![CDATA[<p>Great stuff Franco! For sure I need to put my hands on it <img src='http://www.weblob.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on thx : Arrays by franco</title>
		<link>http://www.weblob.net/2011/thx-arrays/#comment-56</link>
		<dc:creator>franco</dc:creator>
		<pubDate>Mon, 13 Jun 2011 19:26:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.weblob.net/?p=50#comment-56</guid>
		<description>I think that thx tries to stay in the middle between a pure functional paradigm and a more object oriented one. Not sure if that is a good spot to be :)</description>
		<content:encoded><![CDATA[<p>I think that thx tries to stay in the middle between a pure functional paradigm and a more object oriented one. Not sure if that is a good spot to be <img src='http://www.weblob.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on thx : Arrays by Stephane Le Dorze</title>
		<link>http://www.weblob.net/2011/thx-arrays/#comment-55</link>
		<dc:creator>Stephane Le Dorze</dc:creator>
		<pubDate>Mon, 13 Jun 2011 19:21:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.weblob.net/?p=50#comment-55</guid>
		<description>If you have to compare it to Stax, what is the main difference in the approach?</description>
		<content:encoded><![CDATA[<p>If you have to compare it to Stax, what is the main difference in the approach?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

