Fix bug in mjsunit/const-eval-init causing objects to be initialized to undefined.
authorricow@chromium.org <ricow@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 8 Jun 2010 11:20:36 +0000 (11:20 +0000)
committerricow@chromium.org <ricow@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 8 Jun 2010 11:20:36 +0000 (11:20 +0000)
commite0bbcf1e6ef82dc06231de19d914e50fe98071c4
tree1b0d568036a4fd6ef258e455c93d9a7f2739c3cc
parentc7ab2b6aa389a93c2b0be6f17389abd4bbb5e64a
Fix bug in mjsunit/const-eval-init causing objects to be initialized to undefined.

In mjsunit/const-eval-init - testInitSlowCaseExtension a range of objects are initialized to undefined instead of a value because the variable i is within quotes (i.e., the source becommes "a1 = i" instead of "a1 = 1".

This should have no impact on the test, I just stumbled over this on
an unrelated matter.

Review URL: http://codereview.chromium.org/2758002

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@4817 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
test/mjsunit/const-eval-init.js