steveb at mindtouch.com
Fri May 25 13:37:04 EDT 2007
I've been looking for a parser to use in our wiki software, but all
the ones I have found (lua, boo, ...) didn't quite fit for different
reasons. Will your parser expose the AST so that it can plugged into
a custom compilation/execution environment?
Steve G. Bjorg
On May 25, 2007, at 9:16 AM, olivier dufour wrote:
> First, I have done a lexer and start the jay for parser.
> But I really prefer to done it manually but it help to understand
> all part of code.
> I have name the project Mono.JScript.Compiler for moment.
> My Lexer work and NUNIT test work on it but for parser it an other
> I use ECMA-262 v3 to do the lexer and parser.
> OK to change to have the same public interface than M$ compiler.
> I will see it and try to go manually now ;)
> thanks for feed back ;)
> Olivier Dufour
> 2007/5/25, Miguel de Icaza <miguel at novell.com>:
> Hello Olivier,
> > Moonlight.
> > It is just to ask if someone is ever working on it... and if
> there is
> > a place in svn to commit in order to make it open to community for
> > dev ;)
> Is this using the DLR?
> I suggest that you do two things:
> * That you ensure that your publicly visible API matches the
> browser in Visual Studio or using monop2:
> And then dump each type with:
> * You should check this work into the olive module, in the
> olive/class directory.
> * You should write a tokenizer/parser from scratch based on
> the public spec instead of the one that we did in the past,
> I suggest a manually written recursive descendant parser
> or even jay, but I would stay away from antlr which is a
> pretty large dependency to put in the tree
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-devel-list