From the Erlang shell, you can compile a module on the fly using
c("path/to/module.erl"). You can also access this functionality through the
compile module, specifically the
For example, suppose we have a file
myfun() -> io:format("Hello Joe~n").
Now, from the Erlang shell (or some other module!):
See Erldocs on the compile module for more information.
You can do a great deal with the Erlang compiler in runtime. For example, you can dynamically generate code for a module (use
erl_syntax!) and then compile it without even writing it to a file using
(Insert standard speech on great power and great responsibility.)
Will you still be able to hot swap code?
Is it the regular use-case to handle code?
No. Normally Erlang code is compiled ahead of time into BEAM bytecode. Depending on whether Erlang was started in embedded or interactive mode, the modules are either loaded on startup, or dynamically as they are referenced. If you are building a release, you basically have to compile ahead of time.
What benefits does the compiler give you in the end then?
Well, for one thing, we can build compact releases without unnecessary components like the compiler. Of course, we also get all the traditional benefits of ahead-of-time compilation, particularly that of not having to waste time compiling all the time.
To sum it up, unless you fully understand the implications and have a very good reason not to compile your code ahead of time, please follow the standard practices.