I think Haskell is the right language to nail down the semantics of Erlang and to prototype an implementation. For performance, I think Haskell is probably not the right language, because you need high performing low level code. This isn't impossible in Haskell, but the implementations are not geared towards that.
On 8/16/07, Joel Reymont <[EMAIL PROTECTED]> wrote: > > > On Aug 16, 2007, at 1:36 PM, Neil Bartlett wrote: > > > However, wouldn't it be rather difficult, given that there doesn't > > seem to be a publicly available specification for the Erlang VM or the > > BEAM file format > > Very difficult, correct. I use Erlang daily, in fact Erlang is what > brings bread to my table. I want to learn more about the Erlang > insides so I'll simply dig in. > > > Perhaps it would be interesting to look at a slightly more constrained > > problem: can Erlang's message passing model (including distributed > > messaging across a network) and process monitoring facilities be > > replicated in Haskell? > > My ultimate goal is to have a version of the Erlang VM that's > suitable for running trading systems, i.e. one that allows high-speed > numerics. I don't have much interest in replicating OTP in Haskell > and Haskell may ultimately not be the right choice for what I envision. > > Thanks, Joel > > -- > http://wagerlabs.com > > > > > > _______________________________________________ > Haskell-Cafe mailing list > [email protected] > http://www.haskell.org/mailman/listinfo/haskell-cafe >
_______________________________________________ Haskell-Cafe mailing list [email protected] http://www.haskell.org/mailman/listinfo/haskell-cafe
