From 36d22d82aa202bb199967e9512281e9a53db42c9 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 7 Apr 2024 21:33:14 +0200 Subject: Adding upstream version 115.7.0esr. Signed-off-by: Daniel Baumann --- .../direct/var-env-global-lex-non-strict.js | 31 ++++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 js/src/tests/test262/language/eval-code/direct/var-env-global-lex-non-strict.js (limited to 'js/src/tests/test262/language/eval-code/direct/var-env-global-lex-non-strict.js') diff --git a/js/src/tests/test262/language/eval-code/direct/var-env-global-lex-non-strict.js b/js/src/tests/test262/language/eval-code/direct/var-env-global-lex-non-strict.js new file mode 100644 index 0000000000..326923050f --- /dev/null +++ b/js/src/tests/test262/language/eval-code/direct/var-env-global-lex-non-strict.js @@ -0,0 +1,31 @@ +// |reftest| error:SyntaxError +// Copyright (C) 2016 the V8 project authors. All rights reserved. +// This code is governed by the BSD license found in the LICENSE file. +/*--- +esid: sec-evaldeclarationinstantiation +description: Variable collision with global lexical binding +info: | + [...] + 5. If strict is false, then + a. If varEnvRec is a global Environment Record, then + i. For each name in varNames, do + 1. If varEnvRec.HasLexicalDeclaration(name) is true, throw a + SyntaxError exception. + 2. NOTE: eval will not create a global var declaration that would + be shadowed by a global lexical declaration. + [...] +negative: + phase: runtime + type: SyntaxError +flags: [noStrict] +features: [let] +---*/ + +let x; + +// Although the `try` statement is a more precise mechanism for detecting +// runtime errors, the behavior under test is only observable for a direct eval +// call when the call is made from the global scope. This forces the use of +// the more coarse-grained `negative` frontmatter to assert the expected error. + +eval('var x;'); -- cgit v1.2.3