[erlang-questions] overriding code in another application

Vlad Dumitrescu <>
Sat Feb 13 14:50:26 CET 2016


Hi Serge,

This is more or less what I do, except that each version is compiled as a
separate application. This makes it easy to build with rebar. I suppose
that I don't really have to start those applications, just make the code
available in the code path. Thanks!

best regards,
Vlad


On Sat, Feb 13, 2016 at 2:31 PM, Serge Aleynikov <>
wrote:

> ​How about compiling code by different compiler versions and putting the
> produced beams into version-specific directories. ​Then at run time either
> add the proper versioned directory's path into ERL_LIBS, provide it
> explicitely via "-pa", or add it dynamically at run-time via the
> code:add_patha/1 call?
>
> On Fri, Feb 12, 2016 at 9:19 AM, Vlad Dumitrescu <>
> wrote:
>
>> Hi!
>>
>> I need to be able to distribute a version of the debugger in a way that
>> works with R15+, and this is how I made it work: have a general my_debugger
>> application that contains common code and dummy modules that are
>> implemented in separate applications (my_debugger_15 to my_debugger_18),
>> each compiled with the respective compiler.
>>
>> My idea is that I start 'my_debugger' and dynamically the right
>> 'my_debugger_X' and the dummy modules will get reloaded from the _X
>> application.
>>
>> So far it seems to work, but I wonder if there may be some details that I
>> don't see and that would make this a no-go. I won't use releases, but the
>> applications might get stopped. Has anyone ever tried or thought about this?
>>
>> best regards,
>> Vlad
>>
>>
>> _______________________________________________
>> erlang-questions mailing list
>> 
>> http://erlang.org/mailman/listinfo/erlang-questions
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20160213/feac1b88/attachment.html>


More information about the erlang-questions mailing list