4 ms·
I imagine developers as experienced as the creators of this evaluated the C options and decided C++ was in fact not more of a detriment than a gain. It has its
by mouldysammich 6y ago
I imagine developers as experienced as the creators of this evaluated the C options and decided C++ was in fact not more of a detriment than a gain.
It has its problems but blindly being anti C++ is silly.
- metroholografix 6y agoHardly blindly. It's been a C codebase so far. Introducing C++ makes this no longer the case. This has strong implications for both development and deployment. I'm perplexed since there exist battle-tested code generation engines written in C (e.g. dynasm). Correct me if I'm wrong but it doesn't look like asmjit is anything special in that regard. I can't imagine Joe Armstrong being happy about this.
- tluyben2 6y agoHe might roll over in his grave... I do agree with you though.
- jashmatthews 6y agoDynasm depends on Lua for pre-processing into pure C. I guess you could write an Erlang version? There's a Ruby meta-assembler in Safari JavaScriptCore!
- metroholografix 6y agoDynasm can be compiled with minilua.c (a single file), which can simply be embedded into the Erlang build. https://corsix.github.io/dynasm-doc/tutorial.html https://corsix.github.io/dynasm-doc/tutorial.html
- h0l0cube 6y ago"We also considered using dynasm, but found the tooling that comes with asmjit to be better." https://github.com/erlang/otp/pull/2745#issuecomment-691482132 https://github.com/erlang/otp/pull/2745#issuecomment-6914821...
- patrec 6y agoAlready exists, written by none other than Virding himself: https://github.com/rvirding/luerl https://github.com/rvirding/luerl