You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
Compare Esprima's behaviour when parsing the following two programs. Thanks to @edgemaster for the examples.
"use strict";varpublic=1;
"use strict";public=1;
What is the expected output?
A parse failure for both programs.
What do you see instead?
The first program results in a parse failure. The second program is parsed as though 'public' were not a ReservedWord in strict mode. Note that this behaviour does not occur if a non-strict mode only reserved word such as enum is substituted.
What version of the product are you using? On what operating system? Which browser?
Master. This bug can be seen on the online parser demo.
The text was updated successfully, but these errors were encountered:
conrad-watt
changed the title
Strict mode only reserved words in AssignmentExpressions do not cause early errors
Strict mode only reserved words in AssignmentExpressions do not cause parse errors
May 1, 2015
What steps will reproduce the problem?
Compare Esprima's behaviour when parsing the following two programs. Thanks to @edgemaster for the examples.
What is the expected output?
A parse failure for both programs.
What do you see instead?
The first program results in a parse failure. The second program is parsed as though 'public' were not a ReservedWord in strict mode. Note that this behaviour does not occur if a non-strict mode only reserved word such as enum is substituted.
What version of the product are you using? On what operating system? Which browser?
Master. This bug can be seen on the online parser demo.
The text was updated successfully, but these errors were encountered: