Fix unhandlified code calling Harmony Proxy traps.

Fix unhandlified code calling Harmony Proxy traps.

R=rossberg@chromium.org
BUG=v8:2219
TEST=mjsunit/regress/regress-2219

Committed: https://code.google.com/p/v8/source/detail?r=12001

[rossberg, 2012-07-06 09:53:28]

LGTM with comments

https://chromiumcodereview.appspot.com/10703103/diff/1/src/objects.cc
File src/objects.cc (right):

https://chromiumcodereview.appspot.com/10703103/diff/1/src/objects.cc#newcode...
src/objects.cc:2863: // From this point on everything needs to be handlified,
because
Actually, the point is after the special handling of JSGlobalProxy, which does a
recursive call into this same function again.

https://chromiumcodereview.appspot.com/10703103/diff/1/src/objects.cc#newcode...
src/objects.cc:2865: Handle<JSObject> object(this);
Can we call it 'self', like in other places? That's a bit more descriptive.

[Michael Starzinger, 2012-07-06 11:11:12]

Comments addressed. Landing.

https://chromiumcodereview.appspot.com/10703103/diff/1/src/objects.cc
File src/objects.cc (right):

https://chromiumcodereview.appspot.com/10703103/diff/1/src/objects.cc#newcode...
src/objects.cc:2863: // From this point on everything needs to be handlified,
because
On 2012/07/06 09:53:28, rossberg wrote:
> Actually, the point is after the special handling of JSGlobalProxy, which does
a
> recursive call into this same function again.

Done.

https://chromiumcodereview.appspot.com/10703103/diff/1/src/objects.cc#newcode...
src/objects.cc:2865: Handle<JSObject> object(this);
On 2012/07/06 09:53:28, rossberg wrote:
> Can we call it 'self', like in other places? That's a bit more descriptive.

Done. As discussed offline, in the long run this should be named "object" and
passed in as the first argument to a completely handlified method. But as a
interim solution I am fine with naming it "self" for now.