Mon Jul 16 10:35:49 CEST 2007
would be fun.
The first step would be a simple interpretor - from that the compiler
is easy :-)
The difficulty of wring an interpretor seems mainly to do with getting
parse tree of the js source into Erlang - the interpretor should be pretty easy.
If such a parser exists please tell me where to find it !!
Failing this I guess the easiest approach is to take spidermonkey make
version and fix the parser to dump the parse tree in some suitable
I suspect that spidermonkey make C data structures suitable for
rather than parse trees as such.
and put this into yecc
Failing that it's back to the ECMA-262 spec ( I suppose) and try to convert the
grammar in the appendices to something sensible.
In projects like this I always think that writing an accurate parser
is the tricky bit.
On 7/14/07, Joel Reymont <> wrote:
> This is the reason I asked.
> Think scalable web development for the masses.
> On top of Erlang.
> On Jul 13, 2007, at 8:11 PM, denis wrote:
> > We are building an infrastructure allowing giving some services to our
> > users. But external developers (same company, but other teams)
> > could build
> > their own custom services inside the infrastructure. Having these
> > new users
> > to learn a new language to build a custom services (which can be quite
> > simple) can be badly perceived.
> http://topdog.cc - EasyLanguage to C# compiler
> http://wagerlabs.com - Blog
> erlang-questions mailing list
More information about the erlang-questions