mguimas

mguimas

A module X in file /project/lib/x.ex has the following module metadata:

iex(7)> X.module_info()
[
  module: X,
  exports: [__info__: 1, foo: 0, module_info: 0, module_info: 1],
  attributes: [vsn: [259318855844826186809719652690816251721]],
  compile: [
    version: '7.3.1',
    options: [:dialyzer, :no_spawn_compiler_process, :from_core,
     :no_auto_import],
    source: '/project/lib/x.ex'
  ],
  native: false,
  md5: <<195, 22, 254, 181, 205, 81, 155, 43, 204, 133, 244, 77, 11, 5, 183,
    73>>
]

How can one modify the source entry to something else than the name of the file where module X is defined?

I tried

defmodule X do
@compile {:source, "/project/lib/another_file.ex"}
def foo, do: IO.puts "foo"
end

but this has no effect.

Thanks

Showing Posts 1 to 9

NobbZ

NobbZ

@file if I recall correctly. But it’s meant to be used for generated files only, as well as @line.

mguimas

mguimas OP

@file works on a function basis, not for the whole module unfortunately.

tty

tty

The closes I know is to strip the beam.

:beam_lib.strip_files(["Elixir.X.beam"]).

Honestly though I’m not sure why you would want to manipulate the source compile attribute. source and vsn are 2 quick checks in production that you are running the modules you think you should be running.

mguimas

mguimas OP

I want to manipulate it in generated modules, not in those written by hand of course.

michalmuskala

michalmuskala

The solution might be to use Module.create explicitly instead of using defmodule - you can alter the file in the environment passed in there.

mguimas

mguimas OP

I thought about that but there are issues.

For example, if we do like this

q = quote do
def foo, do: 1/0
def bar, do: 2/0
end
Module.create(Y, q, Map.put(__ENV__, :file, "y.ex"))

then when calling Y.foo() and Y.bar() the lines in the stracktraces are the same. I think this is because quote does not add metadata line: number in this case (only when the quotes are generated by the compiler when calling macros do they get the line: number metadata).

I also tried to do quote location: :keep do ... but then the file is the physical file, not y.ex.

The only solution I found is to do Macro.postwalk to add the metadata keep: {"y.ex", number} on every node that has the metadata line: number.

This solution is working well, but a more direct way would be preferable. The possibilities are:

  1. have @file set the file for all following functions and macros, not only the next one

  2. support quote location: "filepath" do and quote lines: true do

In fact, I think both points 1) and 2) would be useful for my and other use cases.

OvermindDL1

OvermindDL1

quote doesn’t, but calling a macro with AST does.

mguimas

mguimas OP

Yep, that’s what I said (unless I expressed myself badly :smile:)

OvermindDL1

OvermindDL1

Just clarifying that quoting into something is not the same as building Macro’s in Elixir (which is oddly different from other languages). ^.^;

— All posts loaded —

Where Next? Top

Trending in Questions Top

katta
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
kpanic
Hi everyone, I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding. I sta...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
apz
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New

Other Trending Topics Top

GenericJam
Edit: 2026 May 15 - This post is archived. Mob is alive!! Main docs: mob v0.7.11 — Documentation A bit of explanation for the slightly c...
New
JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
garrison
Hobbes is a low-level distributed database for the Elixir programming language. Hobbes provides a simple, safe, and scalable storage lay...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
budgie
A little off-topic, but I feel like people here have a good head on their shoulders. I used to be quite good at making software. Was luc...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews