http://icodeblog.com/2011/08/31/grand-central-dispatch-and-writing-methods-that-accept-blocks-as-arguments/ iPhone Programming Tutorials Mon, 18 Aug 2014 06:06:00 +0000 hourly 1 http://wordpress.org/?v=3.9.2 http://icodeblog.com/2011/08/31/grand-central-dispatch-and-writing-methods-that-accept-blocks-as-arguments/#comment-9488 Mon, 10 Sep 2012 18:40:00 +0000 http://icodeblog.com/?p=3385#comment-9488 Nice post! Very helpful.

]]> http://icodeblog.com/2011/08/31/grand-central-dispatch-and-writing-methods-that-accept-blocks-as-arguments/#comment-9339 Sat, 07 Apr 2012 04:47:00 +0000 http://icodeblog.com/?p=3385#comment-9339 Is it better to use this pattern in a run loop rather than blocking a background thread?

]]> http://icodeblog.com/2011/08/31/grand-central-dispatch-and-writing-methods-that-accept-blocks-as-arguments/#comment-8059 Mon, 12 Sep 2011 10:23:00 +0000 http://icodeblog.com/?p=3385#comment-8059 Thanks for the update and yes this new widget is great to work.

]]> http://icodeblog.com/2011/08/31/grand-central-dispatch-and-writing-methods-that-accept-blocks-as-arguments/#comment-8013 Fri, 02 Sep 2011 18:17:00 +0000 http://icodeblog.com/?p=3385#comment-8013 One thing I have trouble wrapping my head around is, when is it necessary to copy the block (e.g. [myblock copy]), and when is it not necessary?  Apple’s docs ( http://bit.ly/qnb9bd ) say, “Typically, you shouldn’t need to copy (or retain) a block. You only need to make a copy when you expect the block to be used after destruction of the scope within which it was declared.”  But in your downloadPlistForURL example, isn’t that the case, and shouldn’t you therefore have to [copy] the block before calling dispatch_async?

]]>