A named function, existing as a variable in its own local scope, shadows the global declaration about js-interpreter HOT 3 CLOSED

Thanks for this. I'm always excited to learn about JS-Interpreter bugs.

Here's a minimal testcase:

function myFunc() {
  myFunc = 42;
}
myFunc();
alert(myFunc);

Browser output: 42
JS-Interpreter output: [object Function]

This will be fixed immediately. Investigating...

from js-interpreter.

There are two bugs here:

1. With function declarations, per example given in the previous comment.
2. With named function expressions:

   alert((function foo() { foo = 42; return foo; })())

   should return the function object in nonstrict mode, and throw TypeError: Assignment to constant variable in strict mode, but in fact returns 42.
   • The name of a named function expression is an immutable binding within the body of the function.)
   • N.B. however that it can be shadowed by a parameter or variable:

     alert((function foo(foo) { foo = 42; return foo;})())
     

     and

     alert((function foo() { var foo = 42; return foo;})())
     

     should both return 42 in either strict or nonstrict mode.

from js-interpreter.

Tested the fix, it works perfectly. Thank you very much!

JS-Interpreter and Blockly are two great projects, your efforts are much appreciated.

If there is a way to send you both a beer or two, please let me know :)

from js-interpreter.