Variable assignment takes place in a block in a block

Question

I first had this code, but it wasn't working:

VIM = Vimrunner::RSpec.configure do |config|
  config.reuse_server = true

  config.start_vim do
    vim = Vimrunner.start
    vim
  end
end

The configure is just a method that does the settings for a Vimrunner server. The start_vim method just depicts, what is supposed to be executed to start vim. However that doesn't really matter.

What was actually correct was:

Vimrunner::RSpec.configure do |config|
  config.reuse_server = true

  config.start_vim do
    VIM = Vimrunner.start
    VIM
  end
end

I don't quite understand this. In the first case I actually assigned a Proc to the VIM constant, as I found out through irb, whereas in the second case, the VIM constant was correctly assigned.

So it seems, I assigned the VIM constant (which lies in the global namespace) through the use of these blocks, and that's where my understanding fails me:

How I can I assign a variable in a block in a block and let that assignment be hurled back to global namespace?

How does that work? For example I tried this code:

def foo
    yield
end

foo do
    a = 'Hello World!'
    a
end

puts a

Which will show me an error. How can I have variables inside ruby blocks be put into the caller's scope?

Nabeel · Accepted Answer · 2016-07-13T22:50:42.680

1

You could use an instance variable if you want to access it outside? i.e. @a = 'Hello World!' and then use puts @a. Local variables are tied to the block you're in itself and thus can not be called outside.

I'm not sure exactly what your use case is, however you should be able to use this instead

def foo
  yield
end

foo { 'Hello World!' }

or in your first case (since it's a configuration setting I'm not sure if it even matters if you need a variable to store this)

Vimrunner::RSpec.configure do |config|
  config.reuse_server = true
  config.start_vim { Vimrunner.start }
  config
end

edited Jul 13 '16 at 22:50

answered Jul 13 '16 at 22:39

Nabeel

2,272
1
11
14

Actually no, that doesn't work. It has to `config.start_vim { vim = Vimrunner.start; vim }`. That's what I find so confusing about it. – hgiesel Jul 13 '16 at 22:44
That seems odd as it's pretty much the same thing. – Nabeel Jul 13 '16 at 22:45
The thing is I continue to use the `VIM` constant (or variable, that really doesn't matter) after that method call. So it's basically impossible to test it. – hgiesel Jul 13 '16 at 23:00

Variable assignment takes place in a block in a block

1 Answers1