Comments on: “AkitaOnRails” On Anatomy of Ruby Blocks/Closures http://rubylearning.com/blog/2007/11/30/akitaonrails-on-anatomy-of-ruby-blocksclosures/ Helping Ruby Programmers become Awesome Wed, 08 Feb 2012 15:25:03 +0000 hourly 1 http://wordpress.org/?v= By: NatashaTheRobot http://rubylearning.com/blog/2007/11/30/akitaonrails-on-anatomy-of-ruby-blocksclosures/comment-page-1/#comment-134049 NatashaTheRobot Mon, 16 Jan 2012 00:05:45 +0000 http://rubylearning.com/blog/2007/11/30/akitaonrails-on-anatomy-of-ruby-blocksclosures/#comment-134049 <span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">"AkitaOnRails" On Anatomy of Ruby Blocks/Closures: http://t.co/Zo1odHe9</span></span> "AkitaOnRails" On Anatomy of Ruby Blocks/Closures: http://t.co/Zo1odHe9

]]> By: dchuk http://rubylearning.com/blog/2007/11/30/akitaonrails-on-anatomy-of-ruby-blocksclosures/comment-page-1/#comment-133265 dchuk Thu, 27 Oct 2011 18:33:05 +0000 http://rubylearning.com/blog/2007/11/30/akitaonrails-on-anatomy-of-ruby-blocksclosures/#comment-133265 <span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">“AkitaOnRails” On Anatomy of Ruby Blocks/Closures http://t.co/eog5YwVB</span></span> “AkitaOnRails” On Anatomy of Ruby Blocks/Closures http://t.co/eog5YwVB

]]> By: Ochronus http://rubylearning.com/blog/2007/11/30/akitaonrails-on-anatomy-of-ruby-blocksclosures/comment-page-1/#comment-131065 Ochronus Thu, 05 May 2011 13:23:27 +0000 http://rubylearning.com/blog/2007/11/30/akitaonrails-on-anatomy-of-ruby-blocksclosures/#comment-131065 I've written a tutorial/review on ruby blocks and closures with code examples, be sure to check it out: <a href='http://blog.mostof.it/why-ruby-part-two-blocks-and-closures/' rel="nofollow">ruby blocks and closures</a> I’ve written a tutorial/review on ruby blocks and closures with code examples, be sure to check it out: ruby blocks and closures

]]> By: Fabio Akita http://rubylearning.com/blog/2007/11/30/akitaonrails-on-anatomy-of-ruby-blocksclosures/comment-page-1/#comment-126758 Fabio Akita Wed, 20 Oct 2010 14:08:33 +0000 http://rubylearning.com/blog/2007/11/30/akitaonrails-on-anatomy-of-ruby-blocksclosures/#comment-126758 Yes, you and Chad are correct. Looking back I really don't remember what I meant to say when I first wrote this article and I agree that it feels strange reading it now. Maybe I should try to rewrite or omit this particular portion. Thanks for the feedback. Yes, you and Chad are correct. Looking back I really don’t remember what I meant to say when I first wrote this article and I agree that it feels strange reading it now. Maybe I should try to rewrite or omit this particular portion. Thanks for the feedback.

]]> By: soluch http://rubylearning.com/blog/2007/11/30/akitaonrails-on-anatomy-of-ruby-blocksclosures/comment-page-1/#comment-126675 soluch Tue, 19 Oct 2010 17:27:11 +0000 http://rubylearning.com/blog/2007/11/30/akitaonrails-on-anatomy-of-ruby-blocksclosures/#comment-126675 Chad Lester is right. There is a conceptual mistake in the article. Ability to accept parameters doesn't differentiate Proc from Method, and even if it would, it wouldn't affect context saving. The difference between Method and Proc class is that Proc can additionally to instance context save local context of a method, where it is defined. In case of Method there is simply no such local context, there is only instance context (self auto-variable). Ruby Method and Proc work a lot like C# delegates and anonymous delegates, only in C# delegate constructor in some cases may be called implicitly, and in Ruby it is explicit. Chad Lester is right. There is a conceptual mistake in the article. Ability to accept parameters doesn’t differentiate Proc from Method, and even if it would, it wouldn’t affect context saving.

The difference between Method and Proc class is that Proc can additionally to instance context save local context of a method, where it is defined. In case of Method there is simply no such local context, there is only instance context (self auto-variable).

Ruby Method and Proc work a lot like C# delegates and anonymous delegates, only in C# delegate constructor in some cases may be called implicitly, and in Ruby it is explicit.

]]>