tyler.durden
/
test262
mirror of https://github.com/tc39/test262.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
test262/test/language/expressions/function/param-eval-strict-body.js

23 lines
680 B
JavaScript
Raw Normal View History

Normalize testcase format This commit normalizes the test case format used across test262. It applies the following transformations: * Convert to YAML for frontmatter * Remove of trailing whitespace * Replace /r/n with /n except in chapters 6 and 7. * Copyright header always uses // comments * new includes attribute replaces $INCLUDE * No implicit assumptions about test environment other than $ERROR. Everything else appears in the include array. This includes "runTestCase" which is now included in a substantial number of tests.
2014-07-22 01:09:02 +02:00
// Copyright (c) 2012 Ecma International. All rights reserved.
Remove links to hg.ecmascript.org
2015-07-17 17:42:45 +02:00
// This code is governed by the BSD license found in the LICENSE file.
Normalize testcase format This commit normalizes the test case format used across test262. It applies the following transformations: * Convert to YAML for frontmatter * Remove of trailing whitespace * Replace /r/n with /n except in chapters 6 and 7. * Copyright header always uses // comments * new includes attribute replaces $INCLUDE * No implicit assumptions about test environment other than $ERROR. Everything else appears in the include array. This includes "runTestCase" which is now included in a substantial number of tests.
2014-07-22 01:09:02 +02:00
/*---
Frontmatter: fixup "info: >" to "info: |"
2018-01-05 18:26:51 +01:00
info: |
Move `throw "…"` for negative parsing errors to a helper function Closes #1634.
2018-09-27 01:18:22 +02:00
Refer 13.1;
Normalize testcase format This commit normalizes the test case format used across test262. It applies the following transformations: * Convert to YAML for frontmatter * Remove of trailing whitespace * Replace /r/n with /n except in chapters 6 and 7. * Copyright header always uses // comments * new includes attribute replaces $INCLUDE * No implicit assumptions about test environment other than $ERROR. Everything else appears in the include array. This includes "runTestCase" which is now included in a substantial number of tests.
2014-07-22 01:09:02 +02:00
It is a SyntaxError if the Identifier "eval" or the Identifier "arguments" occurs within a FormalParameterList
of a strict mode FunctionDeclaration or FunctionExpression.
Add path attribute.
2014-07-25 00:41:42 +02:00
es5id: 13.1-18-s
Normalize testcase format This commit normalizes the test case format used across test262. It applies the following transformations: * Convert to YAML for frontmatter * Remove of trailing whitespace * Replace /r/n with /n except in chapters 6 and 7. * Copyright header always uses // comments * new includes attribute replaces $INCLUDE * No implicit assumptions about test environment other than $ERROR. Everything else appears in the include array. This includes "runTestCase" which is now included in a substantial number of tests.
2014-07-22 01:09:02 +02:00
description: >
StrictMode - SyntaxError is thrown if the identifier 'eval'
appears within a FormalParameterList of a strict mode
FunctionExpression when FuctionBody is strict code
Refactor function literal tests for parsers A number of tests for the parsing of function literals were expressed using `eval`. This made the tests more complex than necessary and also prevented the tests from providing value to ECMAScript parsers. Remove the use of `eval` in the relevant tests and instead express the expectations with literal source text.
2018-02-04 05:12:16 +01:00
negative:
phase: parse
type: SyntaxError
Update handling of directive prologues Some tests specifically concern the application of the `use strict` directive as it appears in JavaScript source code. These tests should *not* be run with the `onlyStrict` flag because relying on the test runner to enable strict mode makes the semantics of the source code irrelevant. Update these tests to use the `noStrict` flag. Other tests concern language semantics that are only valid in strict mode, but the mechanism for enabling strictness is inconseqential. Update these tests to use the `onlyStrict` flag and remove any redundant `use strict` directive prologues contained within. Still other tests are valid both within and outside of strict mode. In keeping with the majority of other tests, do not specify any restrictions on the environments in which these tests may be run.
2015-06-08 23:35:11 +02:00
flags: [noStrict]
Normalize testcase format This commit normalizes the test case format used across test262. It applies the following transformations: * Convert to YAML for frontmatter * Remove of trailing whitespace * Replace /r/n with /n except in chapters 6 and 7. * Copyright header always uses // comments * new includes attribute replaces $INCLUDE * No implicit assumptions about test environment other than $ERROR. Everything else appears in the include array. This includes "runTestCase" which is now included in a substantial number of tests.
2014-07-22 01:09:02 +02:00
---*/
Rename to $DONOTEVALUATE per @leobalter's suggestion
2018-10-11 16:59:24 +02:00
$DONOTEVALUATE();
Normalize testcase format This commit normalizes the test case format used across test262. It applies the following transformations: * Convert to YAML for frontmatter * Remove of trailing whitespace * Replace /r/n with /n except in chapters 6 and 7. * Copyright header always uses // comments * new includes attribute replaces $INCLUDE * No implicit assumptions about test environment other than $ERROR. Everything else appears in the include array. This includes "runTestCase" which is now included in a substantial number of tests.
2014-07-22 01:09:02 +02:00
Refactor function literal tests for parsers A number of tests for the parsing of function literals were expressed using `eval`. This made the tests more complex than necessary and also prevented the tests from providing value to ECMAScript parsers. Remove the use of `eval` in the relevant tests and instead express the expectations with literal source text.
2018-02-04 05:12:16 +01:00
(function (eval) { 'use strict'; });