When processing global vars initialization account for the case of splitted
authorantonm@chromium.org <antonm@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 25 Nov 2009 15:45:37 +0000 (15:45 +0000)
committerantonm@chromium.org <antonm@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 25 Nov 2009 15:45:37 +0000 (15:45 +0000)
commit93d6199de0b12a427c6905a18e81b3238c52b9f8
tree0256b59146a9abbd96e7ae591d6e65bced5b6554
parentc5052399e4fc66af0367fc92521cf98c62bc50b8
When processing global vars initialization account for the case of splitted
global object (using hidden prototypes):

1) setters might be not on the global object itself, but on its prototypes;
2) if property on one of prototypes is readonly, we could shadow it.
Review URL: http://codereview.chromium.org/434035

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@3362 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/runtime.cc