[erlang-questions] Erlang & .NET
Serge Aleynikov
saleyn@REDACTED
Sun Sep 28 15:37:15 CEST 2008
Actually this doesn't address the problem I stated, as otp.net project
already has functions dealing with encoding/decoding terms to/from
external binary format (similar to what erlocaml does).
What I need is a .NET function with this signature:
string_to_eterm(string()) -> term()
I.e. the .NET code analogous to:
{ok, Tokens} = erl_scan:string(Str),
{ok, Term} = erl_parse:parse_term(Tokens),
Term.
I understand that writing an Erlang term parser is probably easier in
OCaml / F# than in .NET, but before spending time on writing one, I
figured I'd first ask the mailing list...
Serge
Ulf Wiger wrote:
> You could stay within the FP fold and port the OCaml
> Erlang term-to-caml type implementation in ErlOcaml
> to F#. (:
>
> http://code.google.com/p/erlocaml/source/browse/trunk/lib/ocamerl/ocamerl/eterm.ml
>
> I have no intuition for whether or not this is a good idea...
>
> BR,
> Ulf W
>
>
> 2008/9/27 Serge Aleynikov <saleyn@REDACTED>:
>> In a recent need to have a rich UI client for some of my UNIX processes,
>> this week I was playing with the otp.net contribution (from jungerl)
>> that implements an Erlang node in .NET. Given limited experience with
>> .NET I was quite impressed with how easy it was to get a node running in
>> .NET that exchanges terms with the Erlang VM. After making some
>> improvements to otp.net I ran into a need to be able to have a shell in
>> the UI to execute ad-hoc commands on a distributed node running
>> elsewhere. I understand that this can be accomplished by passing a
>> string to be evaluated to the Erlang node that would do the parsing and
>> execution, but I'd rather have the parser on the C# side.
>>
>> This brings the question of whether anyone has an open-source
>> implementation of the Erlang term parser in .NET.
>>
>> Serge
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://www.erlang.org/mailman/listinfo/erlang-questions
>>
>
More information about the erlang-questions
mailing list