Compile escripts by default #7348
Conversation
The current default when running an escript is to interpret it using the `erl_eval` module. In the ancient times when escript was invented that made sense. Interpretation would be slower and some language constructs would not work, but execution could start immediately without waiting for the compiler to finish. Nowadays with faster computers it makes less sense. Therefore, in Erlang/OTP 27, change the default to compile the escript. That will require the escript to be executed by an Erlang system that includes the Erlang compiler.
bjorng
added
team:VM
CT Test Results 4 files 211 suites 1h 28m 4s ⏱️ For more details on these failures, see this check. Results for commit e1a5d0e. ♻️ This comment has been updated with latest results. To speed up review, make sure that you have read Contributing to Erlang/OTP and that all checks pass. See the TESTING and DEVELOPMENT HowTo guides for details about how to run test locally. Artifacts// Erlang/OTP Github Action Bot |
|
I have marked this pull request as a draft because as an potential incompatibility it will have to be approved by the OTP Technical Board. I also propose that the interpreted mode should be removed in Erlang/OTP 28. |
|
Is it a lot of work to keep the interpreted mode as a fallback for when the compiler is not available? In small embedded systems it might still be nice to be able to run escripts without including the compiler in those systems. Maybe even we have escripts in applications that don't today need the compiler to be present? |
|
@garazdawi No, there is not a lot of ongoing work to keep the interpretation working, but some language construct don't work (see #7257 for an example). Yes, the embedded systems without an compiler could be a reason that we should not remove the possibility to interpret the code. |
The current default when running an escript is to interpret it using the
erl_evalmodule. In the ancient times when escript was invented that made sense. Interpretation would be slower and some language constructs would not work, but execution could start immediately without waiting for the compiler to finish.Nowadays with faster computers it makes less sense.
Therefore, in Erlang/OTP 27, change the default to compile the escript. That will require the escript to be executed by an Erlang system that includes the Erlang compiler.