Extract Erlang record into Elixir

It looks like you are trying to make your defrecord call from inside of a function like:

def  somefunction() do
  Record.defrecord :record_name...
  …
end

The error says the defrecord call must be moved out of the function, presumably to the level of the module.

IIRC defrecord defines a record, it does not create an instance. Pretty much the same as -record(Name, {...}). in Erlang.

You are right, and Record.extract/2 extracts a keywordlist from a *.hrl, which can be used in Record.defrecord.

But it seems as if he were trying to extract a record from a dependency, so it should be :from_lib instead of :from.

Additionally what @easco said seems to be valid as well:

** (ArgumentError) cannot invoke defmacro/2 inside function/macro

Proof:

iex(1)> defmodule M do              
...(1)>   require Record
...(1)>   def foo() do
...(1)>     Record.defrecord(:foo, [bar: 0])
...(1)>   end
...(1)> end
  iex:1

** (ArgumentError) cannot invoke defmacro/2 inside function/macro
    (elixir) lib/kernel.ex:5150: Kernel.assert_no_function_scope/3
    (elixir) lib/kernel.ex:3906: Kernel.define/4
    (elixir) expanding macro: Kernel.defmacro/2
    iex:5: M.foo/0
    (elixir) expanding macro: Record.defrecord/2
    iex:5: M.foo/0

As you can see, the errormessage has the same shape.

Thanks for responses guys.
Yep, I’m a bit of an idiot.

easco is right, I had put this in a function whereas it should have been at module level. I corrected this and it was fine.

The next thing I am trying to do is populate the record that has been defined.

In Erlang I can do this by doing the following (I need them to go into a list hence the square brackets):

things = [#thing{name = “bob”, age = 30, job = “Elixir Dev”}]

I thought I could do it something like this based on research but I’m probably/most likely wrong (this is without it being a list):

thing2 = thing.new(
name = “bob”,
age = 30,
job = “Elixir Dev”)

You need to import the module that contains the defrecord.

Then you can use the generated macro which has the same name as your record. You can find examples in the documentation of Record.defrecord

IIRC (again) make the argument to new a keyword list. It would become something like:

thing1 = foo(name: "bob", age: 30, job: "Elixir Dev")

Don’t forget that Erlang strings and Elixir strings are not the same.

Thanks again for your help guys. I think I’m starting to get the hang of Elixir now.
I put the extract line into it own module, and imported it and used the syntax in rvirding’s post above and all is working well.

I’m now creating a bigger project but I am still using the same erlang records in it.
However, the extract line will be in a separate app (app1) and I will be calling from a separate app (app2). So app1 will be a dependency in app2. However, when I try and compile I get the following error:

== Compilation error in file lib/app1/mymodule.ex ==
** (RuntimeError) error parsing file deps/mydependency/include/erlangheaderfile.hrl, got: {:error, :enonet}
(elixir) lib/record/extractor.ex:84: Record.Extractor.read_file/2

Its probably something simple that I am missing as it works if I have this in the same app/project. Any ideas what I am doing wrong?

Can you please show the line how you are extracting the record?

And how are you specifiying the dependency in your mixfile?

Sure no problem.

I’m using the same syntax as before with the exception of from_lib now:

Record.defrecord :record_name, Record.extract(:record_name, from_lib: “mydependency/include/header_file.hrl”)

I’m using the standard dependency git syntax in “app1”. Something like this:

{:mydependency, git "git@someurl.git, tag: “atag”, override: true}

in “app2” i’m using the same syntax but to call “app1” as a dependency:

{:app1, git "git@someurlforapp1.git, tag: “atag”, override: true}

I don’t have the :mydependency dependency in “app2”. Should I have?

I hope that helps.

So you are trying to read into a transient dependency this way? I’m not sure if this is possible. Try to add :mydependency in :app2 as well and check if it works.

If not, please try to provide some minimal project(s) at github or otherwise publicly which reproduce the problem such that we can take a deeper look at it.