Currently, a new isolate is created in an uninitialized state, and
authorjochen@chromium.org <jochen@chromium.org>
Mon, 15 Sep 2014 11:17:00 +0000 (11:17 +0000)
committerjochen@chromium.org <jochen@chromium.org>
Mon, 15 Sep 2014 11:17:00 +0000 (11:17 +0000)
commit65a1857824492a2582b9f3638276f9b201529e5d
treeb8e21bf4d08a309f8c1da5df664943dd90bf6d5d
parent734fd70732b85fb5866238a7d0c695b0f901a782
Currently, a new isolate is created in an uninitialized state, and
several API methods will automatically initialize it. During this
uninitialized state, code event handlers and function entry handlers can
be attached to the isolate.

This CL deprecates SetFunctionEntryHook and moves the configuration of
those handlers to the Isolate factory method.

This will allow for initializing the Isolate at creation time in the
future.

Users of V8::SetFunctionEntryHook should pass the entry hook to
Isolate::New instead. V8::SetJitCodeEventHandler should either be passed
to Isolate::New as well, or (if startup events are not required) invoked
via the Isolate.

BUG=none
LOG=y
R=svenpanne@chromium.org

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

git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@23940 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
include/v8.h
src/api.cc
src/d8.cc
src/third_party/vtune/DEPS [new file with mode: 0644]
src/third_party/vtune/v8-vtune.h
src/third_party/vtune/vtune-jit.cc
test/cctest/test-api.cc