Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Elixir macros and bind_quoted

I have a macro that defines a module like so.

defmodule Bar do
  def bar do
    IO.puts "I am #{inspect __MODULE__}"
  end
end

defmodule MacroFun do

  defmacro define_module(name) do
    quote do
      defmodule unquote(name) do
        import Bar
        def foo do
          bar
          IO.puts "I am #{inspect __MODULE__}"
        end
      end
    end
  end

end

defmodule Runner do
  require MacroFun

  def run do
    MacroFun.define_module Foo
    Foo.foo
  end

end

Runner.run

The output of running this is:

I am Bar
I am Runner.Foo

Which makes sense; MacroFun.define_module was called in Runner.run so the module was defined and thus nested under the Runner module.

But now if I change MacroFun.define_module to use the :bind_quoted option:

  defmacro define_module(name) do
    quote bind_quoted: [name: name] do
      defmodule name do
        import Bar
        def foo do
          bar
          IO.puts "I am #{inspect __MODULE__}"
        end
      end
    end
  end

The output now becomes:

I am Bar
I am Foo

Why??

like image 303
cjbottaro Avatar asked Jan 20 '16 00:01

cjbottaro


1 Answers

I think that's because the place where you are unquoting (binding) the variable name.

In the first case, you are unquoting the variable name when creating a module, thus binding the variable at that moment would require to check for context (check if the code is inside another module, for example). So, you get your current atom plus the appropriate context: Runner.Foo.

In the second case, you are unquoting the variable name before it's placed in a context, therefore its value will not change and it'll be the atom Foo (no context).

like image 79
Alex de Sousa Avatar answered Oct 29 '22 14:10

Alex de Sousa