v8/test/message/fail/for-loop-invalid-lhs.out

*%(basename)s:5: SyntaxError: Invalid left-hand side in for-loop
function f() { for ("unassignable" in {}); }
                    ^^^^^^^^^^^^^^
SyntaxError: Invalid left-hand side in for-loop
Remove FLAG_min_preparse_length. It originates from the era where we used to run a separate preparse step before parsing and store the function data. Now the usage of preparser is something completely different, so this flag doesn't make sense any more. In addition, this way we get more test coverage for preparser (for small scripts). BUG= Review-Url: https://codereview.chromium.org/2513563002 Cr-Commit-Position: refs/heads/master@{#41110} 2016-11-18 14:06:25 +00:00			`*%(basename)s:5: SyntaxError: Invalid left-hand side in for-loop`
Align PreParser for loop early error-checking with Parser R=rossberg@chromium.org Review URL: https://codereview.chromium.org/1290193003 Cr-Commit-Position: refs/heads/master@{#30168} 2015-08-13 19:10:59 +00:00			`function f() { for ("unassignable" in {}); }`
			`^^^^^^^^^^^^^^`
[parser] make kInvalidLhsInFor a SyntaxError Second item in section 13.7.5.1 states that the error should be a SyntaxError, when previously CheckAndRewriteReferenceExpression would always emit a ReferenceError. BUG=v8:4373 R=adamk, rossberg LOG=N CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_chromium_rel_ng;tryserver.blink:linux_blink_rel Review URL: https://codereview.chromium.org/1292393002 Cr-Commit-Position: refs/heads/master@{#30184} 2015-08-15 17:57:01 +00:00			`SyntaxError: Invalid left-hand side in for-loop`
Align PreParser for loop early error-checking with Parser R=rossberg@chromium.org Review URL: https://codereview.chromium.org/1290193003 Cr-Commit-Position: refs/heads/master@{#30168} 2015-08-13 19:10:59 +00:00