Fix declarations escaping global strict eval.

Fix declarations escaping global strict eval.

According to ES5 10.4.2(3), eval calls of strict code always require
their own lexical and variable environment. For now we just add a new
scope when we parse the strict mode directive. The clean solution would
be to always have this sope present (even for global eval calls) and
adapt variable binding to cope with that.

R=rossberg@chromium.org
BUG=v8:1624
TEST=mjsunit/regress/regress-1624,test262/S10.4.2.1_A1

Committed: https://code.google.com/p/v8/source/detail?r=11057

[rossberg, 2012-03-14 13:40:05]

Lookgs good so far, but I wonder about the cases where:

- the global scope is in strict mode
- the eval is in a strict function
- the eval is in a non-strict function

...all these cases in combination with all the eval strings you already have.

Can you add these as test cases? Because for some of them, I can't seem to find
any code that would handle them.

[Michael Starzinger, 2012-03-14 13:54:34]

Yes, I can certainly add those test cases. And here are my predictions of what I
think will work and what not.

On 2012/03/14 13:40:05, rossberg wrote:
> - the global scope is in strict mode
We will fail on this.

> - the eval is in a strict function
This will work.

> - the eval is in a non-strict function
This will work.

[rossberg, 2012-03-15 12:47:35]

lgtm