[erlang-questions] Why do "interface to language X" projects all seem to die out?

Vans S vans_163@REDACTED
Wed Aug 31 16:50:03 CEST 2016

You should really be using NIFS to interface with C, C++, Rust and others.

Python is well supported, so apparently is Ruby (I only used python) through erlports. Look at the forks of erlports esp by beano, https://github.com/beano/erlport

Why would you want to use lua. Erlang is a much better replacement. And if you really need Lua then use C Nifs to load + execute the lua. Lua is so simple to integrate, you really don't need an entire library for that, just a simple C NIF. 

    On Wednesday, August 31, 2016 10:18 AM, Matthias Lang <matthias@REDACTED> wrote:


Pretty much all of the "not built in to OTP" ways to connect to other
languages seem to have died, i.e.

  - EPI (C++). Last commit 2009.
  - py_interface (Python). Last commit 2014. Freshest of the lot.
  - edtk (C). Last release 2007.
  - dryverl (C). Last release 2008.
  - erlua (Lua). Project page dead. Author's email is dead.
  - erlualib (last commit 2010). Github-linked company page dead.

Can anyone offer some experiences or ideas why?

Could it be that these types of solutions are rarely needed? Maybe
NIFs are unbeatable for the "narrow interface, no state, high
performance" cases and port programs with hand-rolled interfaces most
of the rest.

erlang-questions mailing list

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20160831/7502ef54/attachment.htm>

More information about the erlang-questions mailing list