Merging about termformat HOT 4 CLOSED

Hi!
Did you take a look at erlport project?
It has fully tested drivers for ruby and python (similar to your erlang_py and erlang_rb).

from termformat.

Yes, I am aware that erlport exists. I wanted to make sure and have a common dependency for the erlang binary term format in a single module, which does happen to be similar to https://github.com/hdima/erlport/blob/master/priv/python2/erlport/erlterms.py, https://github.com/hdima/erlport/blob/master/priv/python3/erlport/erlterms.py, https://github.com/hdima/erlport/blob/master/priv/ruby1.8/erlport/erlterms.rb, and https://github.com/hdima/erlport/blob/master/priv/ruby1.9/erlport/erlterms.rb . However, I wanted to keep the python and ruby code more similar than they are within erlport and keep the term format handling separate from Erlang port usage, so it can be more reusable. The goal with erlang_py and erlang_rb is to have something that is easier to maintain and modify as more things are added to the erlang binary term format with future erlang releases, while not sacrificing efficiency. Compatibility would be handled within a single module to avoid replicating the code, so unfortunately these pursuits don't align themselves with erlport (i.e., no motivation to use different code or have the project change), though it may benefit from some of the same tests.

from termformat.

Uh, good idea.
Unfortunately, i can't merge termformat into your project, because it was written specially for use with BERT-RPC, which uses only basic set of erlang terms (checkout specification).
So i don't need to cover many unused (in BERT) things like references or ports. This keeps code more simple.

from termformat.

Well keep it in mind, you could also try using erlang_py in your project. Just trying to make stuff a bit less fragmented to avoid all the duplicated effort as the binary erlang term format is added to.

from termformat.