On Oct 22, 10:05 am, Attila Szegedi <[EMAIL PROTECTED]> wrote: > I think this is doable by someone who knows the parser innards, but > make sure to raise it as a Bugzilla item otherwise it'll fall off the > radar.
There already seems to be a Rhino bug report for this: https://bugzilla.mozilla.org/show_bug.cgi?id=423557 I recently collected all the bugs involved in making this transition in spidermonkey in a recent posting to this group: http://groups.google.com/group/mozilla.dev.tech.js-engine.rhino/browse_frm/thread/69c5d0fda9808558 And finally I just posted a bug + patch for allowing future reserved by default in Rhino: https://bugzilla.mozilla.org/show_bug.cgi?id=461122 Hannes > Attila. > > On 2008.10.21., at 22:15, Kris Zyp wrote: > > > Is there a way (or could there be a way) to unreserve keywords in the > > property names so that you could use keyword as property names > > (without quoting them in an index operator)? This behavior is > > supported in SpiderMonkey. For example, in SpiderMonkey you can do: > > a.delete = 3; > > But this statement throws an error in Rhino. > > Thanks, > > Kris _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
