http://lostechies.com/derickbailey/2009/09/18/an-alternate-way-to-handle-task-dependencies-in-custom-rake-tasks/ Better Than Yesterday Thu, 13 Jun 2013 17:35:00 +0000 hourly 1 http://wordpress.org/?v=3.4.2 http://lostechies.com/derickbailey/2009/09/18/an-alternate-way-to-handle-task-dependencies-in-custom-rake-tasks/#comment-472 Brian Fri, 18 Sep 2009 15:37:39 +0000 /blogs/derickbailey/archive/2009/09/17/an-alternate-way-to-handle-task-dependencies-in-custom-rake-tasks.aspx#comment-472 In ruby this " => " is not a lambda indicator. It's is the delimiter between key and value in a hash. You're right in stating you can pass ":name => [:dep1, :dep2] " to the rake task method...however, what you're passing is a single argument to that method. The argument is a single-item hash consisting of a key (the left side of the arrow, the task's name in symbol form) and an array as the value (symbols of other names of task dependencies). Actual lamda objects aren't incredibly common in ruby as the are in C# due to blocks, which are similar to lamdas, but not quite the same. The task method ALSO takes a block (indicated by the do/end pair). In ruby this ” => ” is not a lambda indicator. It’s is the delimiter between key and value in a hash. You’re right in stating you can pass “:name => [:dep1, :dep2] ” to the rake task method…however, what you’re passing is a single argument to that method. The argument is a single-item hash consisting of a key (the left side of the arrow, the task’s name in symbol form) and an array as the value (symbols of other names of task dependencies). Actual lamda objects aren’t incredibly common in ruby as the are in C# due to blocks, which are similar to lamdas, but not quite the same. The task method ALSO takes a block (indicated by the do/end pair).

]]>