Handlify ForceSetObjectProperty

Handlify ForceSetObjectProperty

Note that I've left the layering as is to make the diffs clear. Is it worth moving ForceSetObjectProperty to objects.cc? This code is clearly implementing part of the DefineOrRedefine steps from the spec, but it's still odd that it lives in Runtime. Note that handles.cc exposes a ForceSetProperty which just performs a CALL_HEAP_FUNCTION on the Runtime::ForceSetObjectProperty -- which is exposed to the api as v8::Object::ForceSet

BUG=
R=mstarzinger@chromium.org

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

[rafaelw, 2013-11-06 13:03:37]

ptal

[Michael Starzinger, 2013-11-06 14:56:59]

LGTM. Yes, to me personally it makes sense to move this functionality from the
Runtime class into the JSObject class. I don't see a particular reason why they
need/should live in the Runtime class, especially in light that they are used by
the API (i.e. api.cc) as well.

https://codereview.chromium.org/61883002/diff/60001/src/runtime.cc
File src/runtime.cc (right):

https://codereview.chromium.org/61883002/diff/60001/src/runtime.cc#newcode5087
src/runtime.cc:5087: name,
nit: Indentation is off.

[rafaelw, 2013-11-06 16:32:58]

Committed patchset #4 manually as r17529 (presubmit successful).