Fix handling of const initialization. We did not handle the fact that
authorager@chromium.org <ager@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Thu, 22 Jan 2009 13:53:06 +0000 (13:53 +0000)
committerager@chromium.org <ager@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Thu, 22 Jan 2009 13:53:06 +0000 (13:53 +0000)
commitc23dbc1928869b5968877e2fae79834081f4a025
tree54822753618ff1d65b58ea9d4b2a9d54da3228cc
parent0dab442be9ddc125b63419e00c1cedb2bef874dd
Fix handling of const initialization.  We did not handle the fact that
a const variable can be deleted between its declaration and its
initialization.

This fixes issue 189:

  http://code.google.com/p/v8/issues/detail?id=189

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

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1127 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/runtime.cc
test/mjsunit/const-eval-init.js [new file with mode: 0644]
test/mjsunit/const.js
test/mjsunit/regress/regress-189.js [new file with mode: 0644]