Function::Call and Object::CallAsFunction APIs should allow v8::Value as a receiver
authormstarzinger@chromium.org <mstarzinger@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Mon, 30 Sep 2013 11:47:36 +0000 (11:47 +0000)
committermstarzinger@chromium.org <mstarzinger@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Mon, 30 Sep 2013 11:47:36 +0000 (11:47 +0000)
commitf03dbcff949262687073e5764e52ee884b5fa23c
tree5f299f14c863b73f927be18dce6ddb0f8550d0cb
parentf5e783de49a3b6166975c16d04957f84f13f2a06
Function::Call and Object::CallAsFunction APIs should allow v8::Value as a receiver

Since the primitive values can be a receiver of strict mode functions in
ECMA262 5.1th, v8::Function::Call and Object::CallAsFunction should take
v8::Value as a receiver instead of v8::Object.

BUG=v8:2915
TEST=cctest/test-api
R=mstarzinger@chromium.org

Review URL: https://codereview.chromium.org/24920003

Patch from Yusuke Suzuki <yusukesuzuki@chromium.org>.

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17003 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
include/v8.h
src/api.cc
test/cctest/test-api.cc