On Sun, 28 Nov 2004 12:37:03 +0100, James Mastros <[EMAIL PROTECTED]> wrote: > Dan Sugalski wrote: > > Absolutely. Compilers do *not* have to be integrated in with parrot -- my > > current work project uses Parrot as its back end, but the compiler's > > written in perl as a standalone program. Works just fine. (Though a > > Javascript compiler written in Javascript could bootstrap itself pretty > > nicely. That'd be cool... :) > Though integration with the parrot compiler system would be very useful, > both for writing browsers and similar in parrot, and for implementing > javascript's eval() builtin.
We'll see how I'll do it eventually. Right now I've just begun working on a lexer and parser. It would be easy to do if I dropped regular expressions support, but the regular expressions syntax makes the lexer dependent upon the parser. Though I haven't looked into them yet, but I suspect the E4X additions also have such lexer/parser dependencies. -- David "liorean" Andersson <uri:http://liorean.web-graphics.com/>
