Aha. Thanks, I was sure it was sure weird Rhino thing. It's hard to call it valid JavaScript either, though, as it's invalid in every single popular browser. That mozilla doc says "Non-standard. The Iterator function is a SpiderMonkey-specific feature, and will be removed at some point. " As a career JS developer, I simply wasn't going to know to use this non-standard and widely unsupported function. On the other hand, using other modern means, [1] and [2], of iterating the Iterable isn't supported by Rhino .
I guess my point is just that the same syntax patterns a skilled JavaScript developer would expect to use aren't always valid, which creates esoteric knowledge for this environment. Whereas, I felt that all of my existing JS knowledge was usable when I went to other server-side JS solutions, like Node.js for example. -- View this message in context: http://apache-sling.73963.n3.nabble.com/JS-Use-API-usability-or-limitations-tp4069490p4069550.html Sent from the Sling - Users mailing list archive at Nabble.com.
