Comments on: Why ruby? part two – blocks and closures

By: zynasis

zynasis — Fri, 12 Jun 2009 03:11:33 +0000

AGH!!! my eyes are bleeding!!

oh wait, thats just ruby code

By: ochronus

ochronus — Wed, 10 Jun 2009 17:00:01 +0000

@Ethan Thanks for the heads-up, you're absolutely right. I've simplified the example code.

By: Ethan

Ethan — Wed, 10 Jun 2009 14:21:50 +0000

Why are you passing nil to inject? All that does is make “sum” (first parameter) equal nil on the first iteration, requiring you to explicitly check if it’s nil or not in the block’s body.

This is pointless. You don’t need to pass anything:

x.inject { |a,b| a + b }

The correct time to use inject’s parameter when summing is when you are operating on an array of objects, rather than integers. If you pass 0 it will guarantee that the first parameter to the block begins as an integer and stays that way.

For example, given an array x of objects with the property some_int_property:

x.inject(0) { |a,b| a + b.some_int_property }

By: helen

helen — Wed, 10 Jun 2009 09:08:21 +0000

I surly will try it!

By: softmind

softmind — Wed, 10 Jun 2009 06:51:56 +0000

Promoting Ruby:- ” Why ruby ? part two - blocks and closures ” http://tinyurl.com/m8nsc5

This comment was originally posted on Twitter

By: softmind

softmind — Wed, 10 Jun 2009 06:51:56 +0000

Promoting Ruby:- ” Why ruby ? part two – blocks and closures ” http://tinyurl.com/m8nsc5

This comment was originally posted on Twitter

By: ochronus

ochronus — Tue, 09 Jun 2009 20:49:26 +0000

Why ruby? part two - blocks and closures - http://bit.ly/kkBvA

This comment was originally posted on Twitter

By: ochronus

ochronus — Tue, 09 Jun 2009 20:49:26 +0000

Why ruby? part two – blocks and closures – http://bit.ly/kkBvA

This comment was originally posted on Twitter