3 ms·
Oh, I forgot interoperability! I've grown so accustomed to connecting my Erlang programs to C++ libraries through the simplicity of ports that I erred. Thanks
by Scramblejams 14y ago
Oh, I forgot interoperability! I've grown so accustomed to connecting my Erlang programs to C++ libraries through the simplicity of ports that I erred.
Thanks for adding to my list -- the more the merrier. :-)
It would be interesting to make the runtime optional, to see how close together the two runtimey and runtimeless subsets could get. Or, perhaps it would be possible to mark a section of code as runtime-free. IIRC some work's been done on that but I don't think it's ever been practical.
- ihnorton 14y agoDoes Erlang do something special to make C++ interfacing easy? Any info/links would be appreciated - I have only found info about calling C-exported code with ports.
- Scramblejams 14y agoNo, not particularly. I've just settled on writing some shim C/C++ and using msgpack or protobuf over the port to do the interfacing. I prefer it because it feels the simplest to me. Obviously it could get complicated with some applications, though that would be the case with just about any other method of interfacing. Oh, and did I mention my dream language has a great REPL, compiles nearly instantly and can run interpreted, too?
- cpeterso 14y agoA runtime-less subset of Rust is being considered and is being developed incrementally. Most of the Rust compiler and runtime is written in Rust itself, so the runtime may be able to be loaded dynamically. https://github.com/mozilla/rust/issues/3608 https://github.com/mozilla/rust/issues/3608