Esprima Keyword Bug

[IgnoredAmbience]

tests/test262/ch10/10.1/10.1.1/10.1.1-17-s.js:

function testcase() {
        "use strict";
        try {
            var obj = {};
            Object.defineProperty(obj, "accProperty", {
                get: function () {
                    eval("public = 1;");
                    return 11;
                }
            });

            var temp = obj.accProperty === 11;
            return false;
        } catch (e) {
            return e instanceof SyntaxError;
        }
    }
runTestCase(testcase);

stdout:

A variable [__$ERROR__] is defined at global scope.  Its value is:
"runTestCase returned false"

stderr:

Warning:  JsNumber.to_string called.  This might be responsible for errors.  Argument value:  0..
Warning:  JsNumber.to_string called.  This might be responsible for errors.  Argument value:  0..
Warning:  JsNumber.to_string called.  This might be responsible for errors.  Argument value:  0..
Warning:  JsNumber.to_string called.  This might be responsible for errors.  Argument value:  0..
Warning: ref_get_value returns the undefined value on Coq_resvalue_value: undefined
Warning: ref_get_value returns the undefined value on Coq_resvalue_value: undefined

[IgnoredAmbience]

Test aborts on public: NYI.
Test fails on conrad's branch, as above.
Not tested master (yet, not sure if it has been merged through).

[IgnoredAmbience]

This is a bug in esprima. (Thanks again @Pasteuriser)

Try entering into the online parser:

"use strict";
var public = 1;

"use strict";
public = 1;

And observe the discrepancy.

This is still to be reported to esprima.

[conrad-watt]

jquery/esprima#1171

[IgnoredAmbience]

This issue will be fixed in Esprima 2.6.