I’m not sure what you mean - that code from decompilerl depends on the existence of the Abst chunk in the BEAM file it’s used on. If the chunk isn’t there, it’s not going to work.
Each step of the compilation process drops information that’s not important to it, so the process isn’t 100% reversible - for instance, decompilerl uses local variables like _@4 because the original names are not present in the AST.
The Code chunk throws away more information - for instance, the Abst chunk contains AST for “populate a record named :holiday_info” in a function like list_open_total:
list_open_total() ->
[#holiday_total{id = 104,
name = lang:get(<<"HĐ Gộp SV"/utf8>>), type = 2,
start_time = {merge_day, 1},
end_time = {merge_day, 56, 86399}, status = 1,
is_show = 1},
#holiday_total{id = 103,
name = lang:get(<<"HĐ Mở SV"/utf8>>), type = 1,
start_time = {open_day, 1},
end_time = {open_day, 56, 86399}, status = 1,
is_show = 1}].
The corresponding BEAM code from the Code section is “desugared”: the record syntax is shorthand for building a tuple that starts with {:holiday_total, ...:
{:function, :list_open_total, 0, 2,
[
{:label, 1},
{:line, 1},
{:func_info, {:atom, :holiday_role_data}, {:atom, :list_open_total}, 0},
{:label, 2},
{:allocate_zero, 1, 0},
{:move, {:literal, "HĐ Gộp SV"}, {:x, 0}},
{:line, 2},
{:call_ext, 1, {:extfunc, :lang, :get, 1}},
{:move, {:x, 0}, {:y, 0}},
{:move, {:literal, "HĐ Mở SV"}, {:x, 0}},
{:line, 3},
{:call_ext, 1, {:extfunc, :lang, :get, 1}},
{:test_heap, 28, 1},
{:put_tuple, 11, {:x, 1}},
{:put, {:atom, :holiday_total}},
{:put, {:integer, 103}},
{:put, {:x, 0}},
{:put, {:integer, 0}},
{:put, {:literal, {:open_day, 1}}},
{:put, {:literal, {:open_day, 56, 86399}}},
{:put, {:integer, 1}},
{:put, {:integer, 0}},
{:put, {:integer, 0}},
{:put, {:integer, 1}},
{:put, {:integer, 1}},
{:put_list, {:x, 1}, nil, {:x, 1}},
{:put_tuple, 11, {:x, 2}},
{:put, {:atom, :holiday_total}},
...
