ladybird/Libraries/LibJS/Tests/var-scoping.js

load("test-common.js");

try {
  function foo() {
    i = 3;
    assert(i === 3);
    var i;
  }

  foo();

  var caught_exception;
  try {
    j = i;
  } catch (e) {
    caught_exception = e;
  }
  assert(caught_exception !== undefined);

  console.log("PASS");
} catch (e) {
  console.log("FAIL: " + e);
}
js/LibJS: Move test functions to pure javascript. The addition of assert functions to Userland/js was done before we had load(..) implemented. Now that it exists, it seems like the right move the test helper functions to pure javascript instead of poluting js with random global functions. 2020-04-13 10:31:13 -07:00			`load("test-common.js");`

LibJS: Hoist variable declarations to the nearest relevant scope "var" declarations are hoisted to the nearest function scope, while "let" and "const" are hoisted to the nearest block scope. This is done by the parser, which keeps two scope stacks, one stack for the current var scope and one for the current let/const scope. When the interpreter enters a scope, we walk all of the declarations and insert them into the variable environment. We don't support the temporal dead zone for let/const yet. 2020-04-13 16:42:54 +02:00			`try {`
test-js: Use prettier and format all files 2020-07-05 09:27:00 -07:00			`function foo() {`
			`i = 3;`
			`assert(i === 3);`
			`var i;`
			`}`
LibJS: Hoist variable declarations to the nearest relevant scope "var" declarations are hoisted to the nearest function scope, while "let" and "const" are hoisted to the nearest block scope. This is done by the parser, which keeps two scope stacks, one stack for the current var scope and one for the current let/const scope. When the interpreter enters a scope, we walk all of the declarations and insert them into the variable environment. We don't support the temporal dead zone for let/const yet. 2020-04-13 16:42:54 +02:00
test-js: Use prettier and format all files 2020-07-05 09:27:00 -07:00			`foo();`
LibJS: Hoist variable declarations to the nearest relevant scope "var" declarations are hoisted to the nearest function scope, while "let" and "const" are hoisted to the nearest block scope. This is done by the parser, which keeps two scope stacks, one stack for the current var scope and one for the current let/const scope. When the interpreter enters a scope, we walk all of the declarations and insert them into the variable environment. We don't support the temporal dead zone for let/const yet. 2020-04-13 16:42:54 +02:00
test-js: Use prettier and format all files 2020-07-05 09:27:00 -07:00			`var caught_exception;`
			`try {`
			`j = i;`
			`} catch (e) {`
			`caught_exception = e;`
			`}`
			`assert(caught_exception !== undefined);`
LibJS: Hoist variable declarations to the nearest relevant scope "var" declarations are hoisted to the nearest function scope, while "let" and "const" are hoisted to the nearest block scope. This is done by the parser, which keeps two scope stacks, one stack for the current var scope and one for the current let/const scope. When the interpreter enters a scope, we walk all of the declarations and insert them into the variable environment. We don't support the temporal dead zone for let/const yet. 2020-04-13 16:42:54 +02:00
test-js: Use prettier and format all files 2020-07-05 09:27:00 -07:00			`console.log("PASS");`
LibJS: Hoist variable declarations to the nearest relevant scope "var" declarations are hoisted to the nearest function scope, while "let" and "const" are hoisted to the nearest block scope. This is done by the parser, which keeps two scope stacks, one stack for the current var scope and one for the current let/const scope. When the interpreter enters a scope, we walk all of the declarations and insert them into the variable environment. We don't support the temporal dead zone for let/const yet. 2020-04-13 16:42:54 +02:00			`} catch (e) {`
test-js: Use prettier and format all files 2020-07-05 09:27:00 -07:00			`console.log("FAIL: " + e);`
LibJS: Hoist variable declarations to the nearest relevant scope "var" declarations are hoisted to the nearest function scope, while "let" and "const" are hoisted to the nearest block scope. This is done by the parser, which keeps two scope stacks, one stack for the current var scope and one for the current let/const scope. When the interpreter enters a scope, we walk all of the declarations and insert them into the variable environment. We don't support the temporal dead zone for let/const yet. 2020-04-13 16:42:54 +02:00			`}`