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&maxdepth=1&hide_resolved=0
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
Great to hear! What I and Andreas Bolka have done so far has been
relatively simple and should be easy to adapt:
https://bugzilla.mozilla.org/show_bug.cgi?id=456389
https://bugzilla.mozilla.org/show_bug.cgi?id=456357
https://bugzilla.mozilla.org/show_bug.cgi?id=454505
plus a few fixes for destructuring assignments:
https://bugzilla.mozilla.org/show_bug.cgi?id=417568
https://bugzilla.mozilla.org/show_bug.cgi?id=454969
https://bugzilla.mozilla.org/show_bug.cgi?id=436731
hannes
> Thanks,
> Norris