On Thu, Nov 13, 2008 at 7:00 AM, Hannes Wallnoefer <[EMAIL PROTECTED]> wrote:
> 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. The ES3.1 proposed document, which is down to almost just typo fixes apparently, still has the future reserved words in section 7.5.3. There is a note they will add "const", "let" and "yield". So I won't be using any of those words for identifiers as there is inherent risk for the future (although if they are adding to the list then there is risk with other identifiers anyway.) It would be nice to be able to do foo.class without a problem. I know Douglas Crockford thought that should be acceptable. I don't know if the ES3.1 document allows this. Peter _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
