Karl Nilsson

Yes the BCL is effectively out of scope although it will generate mod calls which you can fill in with erlang implementations. You can interact with the existing erlang apis...

With a 3rd child arrived, 9 months of house renovations and a challenging full-time job this project has not progressed. :) Who knows what the new year will bring though....

A record might work. Depends on what data you need.

The type you return is effectively opaque to the caller as it will be passed to the member function as it's first parameter. I'd suggest you write a simple example....

Yes you need to implement the function as generated as an erlang module in src On Fri, 30 Jun 2017 at 17:59, rascala wrote: > Sorry, been a bit busy!...

You probably want to pull the latest changes As there are potential changes to how objects are constructed.

See this as an example. https://github.com/kjnilsson/fez/blob/master/src/System.Lazy_1.erl

Cool. It's fine to have them all in src. It's typical of erlang. Subdirectories add very little IMO. On Sun, 2 Jul 2017 at 15:18, rascala wrote: > Thanks, >...

@rascala I just made some significant changes to how functions and modules are generated which may affect the work you have in progress. I'd recommend you pull and check the...

Manual memory management just doesn't play nicely with the erlang vm typically.