Ruby syntax oddity

Question

Possible Duplicate:
conditional statement and assigning value in ruby

While refactoring some rails code, I have encountered some syntax oddity in ruby.

Given the following method

def get_value
  42
end

Why does this work?

if value = get_value
  puts value
end

While this does not?

puts value if value = get_value

The latter gives an error: undefined local variable or method `value' for main:Object (NameError). I thought these expressions were equal? When the if-block is evaluated before the puts, value should not be undefined.

[This answer should help](http://stackoverflow.com/a/4500597/499609). — Asherah, Jul 25 '12 at 12:31
@DGM: I had the exact same feeling! I just spent the last 9 minutes searching for a dupe, and none seemed to come up. — Asherah, Jul 25 '12 at 12:32
[This one](http://stackoverflow.com/questions/2291646/in-ruby-why-wont-foo-true-unless-definedfoo-make-the-assignment) should also be helpful. — Asherah, Jul 25 '12 at 12:32
Found it: http://stackoverflow.com/questions/1380331/conditional-statement-and-assigning-value-in-ruby — DGM, Jul 25 '12 at 12:38
if value = get_value statement will always return get_value so it will always be true — carpamon, Jul 25 '12 at 12:50

DGM · Accepted Answer · 2012-07-25T14:35:58.877

4

It's due to the parsing of lines, vs execution time. In the first version, value is parsed and set and then the puts evaluated. In the second line, when the parser gets to the variable puts value, it has not yet been defined. In other words, it can't run the line to set the variable, until it has first parsed the line.

edited Jul 25 '12 at 14:35

answered Jul 25 '12 at 12:34

DGM

26,629
7
58
79

Ruby syntax oddity

1 Answers1

Linked