Warn about usage of proprietary js1.2 keywords "export" and "import"

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Seemingly-innocuous variable names "export" and "import" do not get
keyword warning face.

What is the expected output? What do you see instead?
It would be useful if declarations like "var export = true" or "var import
= true" show up in red, as "var function = true;", for instance, does.

What version of the product are you using? On what operating system?
js2-20080616a.el

Please provide any additional information below.
Code like the above two examples throw a "SyntaxError: missing name in
(export|import) statement" in the compilation stage on Mozilla browsers --
https://developer.mozilla.org/en/Core_JavaScript_1.5_Reference/Statements/export
and
https://developer.mozilla.org/en/Core_JavaScript_1.5_Reference/Statements/import
feature more docs. (Not a part of ECMA-262; proprietary ancient cruft left
there since the days of Netscape 3 / Javascript 1.2.) Warning about this
while writing the code saves treacherous debugging.

Original issue reported on code.google.com by oyas...@gmail.com on 19 Mar 2009 at 6:15

[GoogleCodeExporter]

This issue was closed by r72.

Original comment by steve.ye...@gmail.com on 23 Jul 2009 at 11:02

• Changed state: Fixed

[GoogleCodeExporter]

Fixed in svn -- will be part of next release.

Original comment by steve.ye...@gmail.com on 23 Jul 2009 at 11:04