1420002 - Have Debugger.Frame.eval construct scope chain for EvalSharedContext

Status: NEW

(Core :: JavaScript Engine, enhancement, P3)

Description

[Ted Campbell [:tcampbell]]

As Jason pointed out in Bug 1397049, the comments didn't make a lot of sense. It seems that the code doesn't make a huge amount of sense either.

There should be further testing in of how the debugger eval interacts with different language features such as nested evals, arrow functions, and with blocks. I'd also like to see further testing around lexical scopes and debug evals inside them. Testing around creating functions in a debugger environment and then assigning them to an existing binding so script can interact after the debugger is done would be interesting too.

I also would like to propose that the hack in EvalSharedContext been removed and instead (debugger) EvaluateInEnv conjure up an appropriate environment. The debug eval environment has some subtleties and I would rather we explicitly create the scope chain / environment chain in EvaluateInEnv. I'm not sure anyone can give an accurate answer right now for what the debug eval environment and parse context is for our users.