joyent/node — Issue #2214: `undefined = function(){}` causes abort of code execution
Author: pimvdb
Created: 2011-11-28 16:07:34+00:00
State: open

I know `undefined` should not be set to something else than it's inital value, but the following behaviour does seem to be buggy. (I'm on Windows; not sure about other platforms.)

The problem is setting `undefined` to a function:

undefined = function() {};
console.log("This log is not logged");

The log is never logged.

Additionally, when you run `node` and then evaluate the code by typing it in the command prompt, it causes a hang - you cannot type anymore and you have to quit Node.

It seems a regression from 0.5.7 to 0.5.8 because 0.5.8 is the version which doesn't handle this correctly anymore.