On Sep 8, 7:31 am, Hannes Wallnoefer <[EMAIL PROTECTED]> wrote: > I'd like to bring up the topic of JavaScript 1.8 support for Rhino. > The Rhino Whish List wiki page [1] does not even mention JS 1.8, but > it seems like a logical next step, especially since the plans for > EcmaScript 4 have come tumbling down lately. I also think that version > parity with Firefox 3 would benefit many projects using Rhino. > > The JS 1.8 feature that is triggering my request is the object > destructuring shorthand (bug 404734) [2] which would come very handy > for import-property-x-from-module-y functionality in Helma NG. I've > started investigating on this and will try to get something working > soon. I can't promise anything as the Rhino parser is still pretty > unfamiliar to me. > > So what do others think about JS 1.8 support in Rhino, and effort do > you think would be required? From the "what's new in js 1.8" page [3] > and the js 1.8 tracking bug [4] it doesn't look too overwhelming. > > [1]http://developer.mozilla.org/en/Rhino_Wish_List > [2]https://bugzilla.mozilla.org/show_bug.cgi?id=404734 > [3]http://developer.mozilla.org/en/New_in_JavaScript_1.8 > [4]https://bugzilla.mozilla.org/showdependencytree.cgi?id=380236&maxdept... > > Hannes
Yes, JS 1.8 would be nice to have, and like you say, doesn't seem like too much work. I'm working on landing Steve Yegge's changes to the parser for a rational AST. This code makes major changes to the parser, so don't spend too much time on parser changes beforehand. Thanks, Norris _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
