79a98de9f7
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 Review URL: https://chromiumcodereview.appspot.com/9703021 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@11057 ce2b1a6d-e550-0410-aec6-3dcde31c8c00 |
||
|---|---|---|
| .. | ||
| harness-adapt.js | ||
| README | ||
| test262.status | ||
| testcfg.py | ||
This directory contains code for binding the test262 test suite into the v8 test harness. To use the tests check out the test262 tests from http://hg.ecmascript.org/tests/test262 at revision 309 as 'data' in this directory. Using later version may be possible but the tests are only known to pass (and indeed run) with that revision. hg clone -r 309 http://hg.ecmascript.org/tests/test262 data If you do update to a newer revision you may have to change the test harness adapter code since it uses internal functionality from the harness that comes bundled with the tests. You will most likely also have to update the test expectation file.