<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Disqus - Friends of Jaykul</title><link>http://disqus.com/people/Jaykul/</link><description></description><language>en</language><lastBuildDate>Fri, 14 Aug 2009 14:15:14 -0000</lastBuildDate><item><title>Re: Every Friday, rain or shine (Scripting News)</title><link>http://www.scripting.com/stories/2009/08/13/everyFridayRainOrShine.html#comment-14843700</link><description>Indeed, I perhaps shouldn't have employed the wording "either that or".  Nevertheless, I still think that both full blogging and comment threads are solutions, even if perhaps to different problems.  I'll continue to employ both.  :)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Pistos</dc:creator><pubDate>Fri, 14 Aug 2009 14:15:14 -0000</pubDate></item><item><title>Re: Every Friday, rain or shine (Scripting News)</title><link>http://www.scripting.com/stories/2009/08/13/everyFridayRainOrShine.html#comment-14842740</link><description>I hope nothing bad happens to FriendFeed, I really like it. :(  But certainly, I'm of the opinion that we should posting more than just to microblogs.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Pistos</dc:creator><pubDate>Fri, 14 Aug 2009 13:56:49 -0000</pubDate></item><item><title>Re: Ruby Best Practices - Blog</title><link>http://blog.rubybestpractices.com/posts/rklemme/002_Writing_Block_Methods.html#comment-8817440</link><description>Robert: Ah, of course!  Well that's certainly one situation you'd want to use it.  However, I'm not sure how often I'd find myself in that situation.  :)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Pistos</dc:creator><pubDate>Wed, 29 Apr 2009 13:23:52 -0000</pubDate></item><item><title>Re: Ruby Best Practices - Blog</title><link>http://blog.rubybestpractices.com/posts/rklemme/002_Writing_Block_Methods.html#comment-8567785</link><description>You can't take what is in the ensure block and put it after the end of begin-end.  This code example should elucidate:&lt;br&gt;&lt;br&gt;&lt;code&gt;&lt;br&gt;begin&lt;br&gt;  puts 1&lt;br&gt;  raise "Oh no!"&lt;br&gt;rescue Exception =&amp;gt; e&lt;br&gt;  puts 2&lt;br&gt;  raise e&lt;br&gt;ensure&lt;br&gt;  puts 3&lt;br&gt;end&lt;br&gt;puts 4&lt;br&gt;&lt;/code&gt;&lt;br&gt;&lt;br&gt;Output:&lt;br&gt;&lt;br&gt;&lt;code&gt;&lt;br&gt;1&lt;br&gt;2&lt;br&gt;3&lt;br&gt;-:3: Oh no! (RuntimeError)&lt;br&gt;&lt;/code&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Pistos</dc:creator><pubDate>Wed, 22 Apr 2009 09:01:27 -0000</pubDate></item><item><title>Re: Ruby Best Practices - Blog</title><link>http://blog.rubybestpractices.com/posts/rklemme/002_Writing_Block_Methods.html#comment-8567559</link><description>ehsanul: I think you misunderstood my question.  :)  Perhaps a code example will help.  I was wondering why we need this:&lt;br&gt;&lt;br&gt;&lt;code&gt;&lt;br&gt;    begin  &lt;br&gt;      do_work&lt;br&gt;      something_at_end_of_begin_block&lt;br&gt;    rescue Exception =&amp;gt; e  &lt;br&gt;    else  &lt;br&gt;      something_in_else_block&lt;br&gt;    end&lt;br&gt;&lt;/code&gt;&lt;br&gt;    &lt;br&gt;When we can do this instead:&lt;br&gt;    &lt;br&gt;&lt;code&gt;&lt;br&gt;    begin  &lt;br&gt;      do_work&lt;br&gt;      something_at_end_of_begin_block&lt;br&gt;      something_in_else_block&lt;br&gt;    rescue Exception =&amp;gt; e  &lt;br&gt;    end&lt;br&gt;&lt;/code&gt;&lt;br&gt;&lt;br&gt;(Gah, can't format code blocks.  Disqus: fail)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Pistos</dc:creator><pubDate>Wed, 22 Apr 2009 08:50:37 -0000</pubDate></item></channel></rss>