From 5f8de423f190bbb79a62f804151bc24824fa32d8 Mon Sep 17 00:00:00 2001
From: "Matt A. Tobin" <mattatobin@localhost.localdomain>
Date: Fri, 2 Feb 2018 04:16:08 -0500
Subject: Add m-esr52 at 52.6.0

---
 js/src/tests/ecma/ExecutionContexts/10.1.4-10.js | 70 ++++++++++++++++++++++++
 1 file changed, 70 insertions(+)
 create mode 100644 js/src/tests/ecma/ExecutionContexts/10.1.4-10.js

(limited to 'js/src/tests/ecma/ExecutionContexts/10.1.4-10.js')

diff --git a/js/src/tests/ecma/ExecutionContexts/10.1.4-10.js b/js/src/tests/ecma/ExecutionContexts/10.1.4-10.js
new file mode 100644
index 000000000..ea6a4299b
--- /dev/null
+++ b/js/src/tests/ecma/ExecutionContexts/10.1.4-10.js
@@ -0,0 +1,70 @@
+/* -*- indent-tabs-mode: nil; js-indent-level: 2 -*- */
+/* This Source Code Form is subject to the terms of the Mozilla Public
+ * License, v. 2.0. If a copy of the MPL was not distributed with this
+ * file, You can obtain one at http://mozilla.org/MPL/2.0/. */
+
+
+/**
+   File Name:          10.1.4-10.js
+   ECMA Section:       10.1.4 Scope Chain and Identifier Resolution
+   Description:
+   Every execution context has associated with it a scope chain. This is
+   logically a list of objects that are searched when binding an Identifier.
+   When control enters an execution context, the scope chain is created and
+   is populated with an initial set of objects, depending on the type of
+   code. When control leaves the execution context, the scope chain is
+   destroyed.
+
+   During execution, the scope chain of the execution context is affected
+   only by WithStatement. When execution enters a with block, the object
+   specified in the with statement is added to the front of the scope chain.
+   When execution leaves a with block, whether normally or via a break or
+   continue statement, the object is removed from the scope chain. The object
+   being removed will always be the first object in the scope chain.
+
+   During execution, the syntactic production PrimaryExpression : Identifier
+   is evaluated using the following algorithm:
+
+   1.  Get the next object in the scope chain. If there isn't one, go to step 5.
+   2.  Call the [[HasProperty]] method of Result(l), passing the Identifier as
+   the property.
+   3.  If Result(2) is true, return a value of type Reference whose base object
+   is Result(l) and whose property name is the Identifier.
+   4.  Go to step 1.
+   5.  Return a value of type Reference whose base object is null and whose
+   property name is the Identifier.
+   The result of binding an identifier is always a value of type Reference with
+   its member name component equal to the identifier string.
+   Author:             christine@netscape.com
+   Date:               12 november 1997
+*/
+var SECTION = "10.1.4-10";
+var VERSION = "ECMA_1";
+startTest();
+
+writeHeaderToLog( SECTION + " Scope Chain and Identifier Resolution");
+
+new TestCase( "SECTION", "MYOBJECT.toString()" );
+
+test();
+
+function test() {
+  for ( gTc=0; gTc < gTestcases.length; gTc++ ) {
+    var VALUE = 12345;
+    var MYOBJECT = new Number( VALUE );
+
+    with ( MYOBJECT ) {
+      gTestcases[gTc].actual = toString();
+      gTestcases[gTc].expect = String(VALUE);
+    }
+
+    gTestcases[gTc].passed = writeTestCaseResult(
+      gTestcases[gTc].expect,
+      gTestcases[gTc].actual,
+      gTestcases[gTc].description +" = "+
+      gTestcases[gTc].actual );
+
+    gTestcases[gTc].reason += ( gTestcases[gTc].passed ) ? "" : "wrong value ";
+  }
+  return ( gTestcases );
+}
-- 
cgit v1.2.3