<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt"><div>Thank you both for the answers.<br></div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><br><div style="font-family: arial,helvetica,sans-serif; font-size: 13px;"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Kenneth Lundin <kenneth.lundin@gmail.com><br><b><span style="font-weight: bold;">To:</span></b> Pablo Platt <pablo.platt@yahoo.com><br><b><span style="font-weight: bold;">Cc:</span></b> erlang-questions@erlang.org<br><b><span style="font-weight: bold;">Sent:</span></b> Wednesday, December 17, 2008 6:26:12 PM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [erlang-questions] compile a module against a different otp minor version<br></font><br>
Hi,<br><br>Here is a repetition of an answer I gave about a year ago.<br><br>The safe assumption that we design and test for as good we can is that<br>a .beam file compiled with the release including erts-5.5.3 will run on all<br>forthcoming 5.5.x (x > 3) releases and even on 5.6.x releases if we<br>don't explicitly<br>state otherwise.<br>But note, that even if a .beam file produced with an erts-5.5.x (R11B<br>something) system works on a erts-5.6.x (R12B something) system it<br>might not run as efficient as the same .beam file produced with an<br>erts-5.6 system.<br>Because of this I would recommend that you build new .beam files when<br>there is a new major release.<br><br>It is actually both the erts version and the compiler version that is<br>importan when<br>it comes to compatibility.<br><br>Even if it works in most cases I would not say that is a 100% safe<br>assumption to<br>say that a .beam file produced with a newer release will run
without<br>problems on an older release. It may hold for one module but maybe not<br>for another depending on<br>the contents of the module.<br><br>Our strategy is to be compatible with at least one older major version.<br>R11B can run code from R9C and R10B<br>within a major release like R11B .beam files produced by a release say<br>R11B-0 can always be run by systems R11B-1 and newer.<br><br>/Kenneth (Erlang/OTP team at Ericsson)<br><br>2008/12/17 Pablo Platt <<a ymailto="mailto:pablo.platt@yahoo.com" href="mailto:pablo.platt@yahoo.com">pablo.platt@yahoo.com</a>>:<br>> Hi,<br>><br>> Is it possible to compile a module against a different minor otp version<br>> that the one the module is going to run in?<br>> For example, if I have R12B-3 can I run a module compiled using R12B-5?<br>><br>> How can I find out the minor version of the OTP?<br>> I've tried both:<br>> erlang:system_info(otp_release).<br>>
init:script_id().<br>><br>> but they only reveal R12B.<br>><br>> Thanks<br>><br>><br>> _______________________________________________<br>> erlang-questions mailing list<br>> <a ymailto="mailto:erlang-questions@erlang.org" href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>> <a href="http://www.erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://www.erlang.org/mailman/listinfo/erlang-questions</a><br>><br></div></div></div><br>
</body></html>