[erlang-questions] Erlang and Akka

[Vlad Dumitrescu]

On Tue, Sep 2, 2014 at 5:41 PM, Norton Joseph Wayne <
norton@REDACTED> wrote:

> As an example, the implementation of UBF on GitHub (
> http://ubf.github.io/ubf/ubf-user-guide.en.html) supports several network
> formats including UBF(A), Erlang binary format (a.k.a. EBF), and a local
> procedure call (a.k.a. LPC).  The network formats share the same contract
> checker implementation.
>

I saw later your note about the project. Great stuff! It would need a bit
more of marketing, though :-)

best regards,
Vlad



On Tue, Sep 2, 2014 at 5:41 PM, Norton Joseph Wayne <
norton@REDACTED> wrote:

>
> A few comments.
>
> On 2014/09/02, at 21:13, Vlad Dumitrescu <vladdu55@REDACTED> wrote:
>
> On Mon, Sep 1, 2014 at 11:06 PM, Wojtek Narczyński <wojtek@REDACTED>
> wrote:
>
>    - should the contract checker be hard-linked to UBF(A), the wire
>    format? If used only internally, it seems reasonable to let it understand
>    the Erlang binary format
>
> As an example, the implementation of UBF on GitHub (
> http://ubf.github.io/ubf/ubf-user-guide.en.html) supports several network
> formats including UBF(A), Erlang binary format (a.k.a. EBF), and a local
> procedure call (a.k.a. LPC).  The network formats share the same contract
> checker implementation.
>
> This contract checker implementation operates directly on Erlang terms.
>  There is a lot of surrounding code but the core of the checker is a
> function that checks Erlang terms against a contract (
> https://github.com/ubf/ubf/blob/master/src/contracts.erl#L108).
>
>
>    - since 2002, Erlang got type descriptions and specifications; should
>    these be used for describing the protocols? Again, it seems reasonable to
>    be able to refer to existing types from the source code.
>
>
> Yes, agreed.
>
>
>    - should it be possible to turn the contract checker on and off,
>    preferably without performance impact when off?
>
> Yes, agreed.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140902/1861ce1c/attachment.htm>