[erlang-questions] Feedback wanted: Remove compilation times from BEAM files in OTP 19?

Éric Pailleau eric.pailleau@REDACTED
Fri Apr 8 14:11:05 CEST 2016

Beam files are separated in different chunks.
All dynamic information should be placed in a separate chunck Mho.
And sha1sum of code part, or checksum of its canonical abstract code maybe available in a chunk, existing or new one. 
This could allow to know that a beam, even without the same checksum on the file globally,  run the same code than another Beam file, and so be able to do some Nix like distribution. 

Compiler version allow to estimate what Erlang version compiled the beam. This is something to keep I think. 


"Envoyé depuis mon mobile " Eric

---- Matthias Rieber a écrit ----

>On Fri, 8 Apr 2016, Björn Gustavsson wrote:
>> As long as anyone can remember, the compilation time has been included
>> in BEAM files (and can be retrieved using module_info()).
>> As far as I know, the inclusion of the time has only caused problems.
>> I can't remember that anyone has found any use for the compilation
>> time.
>> So if we decide to remove the compilation time by default in OTP 19...
>> ... would it cause any problem for someone in some workflow?
>I couldn't resist:
>erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20160408/3d7cbdf4/attachment.htm>

More information about the erlang-questions mailing list