Fixed evaluation order issue in defineProperties.
authorsvenpanne@chromium.org <svenpanne@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 19 Oct 2011 09:52:08 +0000 (09:52 +0000)
committersvenpanne@chromium.org <svenpanne@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 19 Oct 2011 09:52:08 +0000 (09:52 +0000)
commitd0fe04447e8dfd9ae8df6d586e23d2a391a7d6a4
tree9d03569f5ef60cb6fa907fa1a0205b9460c65427
parentb3eba9e764a093e4c13d70cdcf240c925a18dc91
Fixed evaluation order issue in defineProperties.

This is not covered by test262 yet, but it really makes sense and matches Firefox's behaviour.

TEST=mjsunit/define-properties.js
Review URL: http://codereview.chromium.org/8349031

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9694 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/v8natives.js
test/mjsunit/object-define-properties.js