Fix issue 191:
authorager@chromium.org <ager@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Thu, 15 Jan 2009 11:31:08 +0000 (11:31 +0000)
committerager@chromium.org <ager@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Thu, 15 Jan 2009 11:31:08 +0000 (11:31 +0000)
commit384b0a5408f25079c40cce1b75c6007b77a09854
treea1dc5df6e8bf0d0e81c476df21a571702d7b5c46
parent958316400f859ae1b079559f9d2e62d022a1cb19
Fix issue 191:

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

Accessor setters should not be called for eval-introduced context
extension objects.

This change fixes the issue, but I think it is time to separate out
the lookup routines for eval-introduced context extension objects.
There is no reason to use the general lookup routines for this.  I'll
do that in a separate changelist.
Review URL: http://codereview.chromium.org/18090

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1076 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/objects.cc
test/mjsunit/regress/regress-191.js [new file with mode: 0644]