These are some features that I'm quite excited and sufficiently confident about, but I'd like to hear some other opinions about before committing.
https://bugzilla.mozilla.org/show_bug.cgi?id=462827 - Do not wrap JavaAdapter that implement Scriptable This is a very clever (and small) hack to not wrap JavaAdapters when the class implements org.mozilla.javascript.Scriptable. The allows to extend JS objects from within JavaScript very easily and elegantly. The bug has an attached demo script that shows how this can be used to implement a "JSAdapter". I can't think of any contraindications, i.e. cases where you'd want to handle a Scriptable object as Java object. https://bugzilla.mozilla.org/show_bug.cgi?id=448816 - Implement Map interface in ScriptableObject This allows ScriptableObjects to be accessed as java.util.Map from Java. The current implementation is somewhat limited as put() is not supported. It also doesn't implement equals() and hashCode() as suggested by the java.util.Map API, as making these dependent on the object's properties might easily break existing code. Even so, this should be very useful to move data between JS and Java. https://bugzilla.mozilla.org/show_bug.cgi?id=461122 - Allow future reserved words as identifiers by default Not being able to use any Java reserved word in JavaScript has been one of my pet peeves. By now, all browser JS engines I know about allow the use of future reserved words as defined by EcmaScript 7.5.3, and I think Rhino should catch up with them. The patch also allows use of "import" and "export" which are still reserved in Spidermonkey, but have no special meaning in Rhino. What do you think? Hannes _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
