Make the Isolate parameter mandatory in Locker and Unlocker classes.

Make the Isolate parameter mandatory in Locker and Unlocker classes.

Note that leaving out the Isolate parameter previously had a very special
meaning, namely "use the *default* Isolate", i.e. the one magically created at
program initialization time. All other API entries use the meaning "current
Isolate", which is different in a multi-threaded setting and confusing.

Temporarily disabled deprecations until Chrome is ready.

BUG=v8:2487
Committed: http://code.google.com/p/v8/source/detail?r=13419

[Michael Starzinger, 2013-01-17 10:53:18]

LGTM (with a nit).

https://chromiumcodereview.appspot.com/11970009/diff/1/src/isolate.h
File src/isolate.h (right):

https://chromiumcodereview.appspot.com/11970009/diff/1/src/isolate.h#newcode1074
src/isolate.h:1074: // to create a Locker for the first time (the lock itself is
in the isolate).
I guess in the long run this method should disappear completely. Can we add a
TODO about that?

[Sven Panne, 2013-01-18 07:20:04]

Landing...

https://chromiumcodereview.appspot.com/11970009/diff/1/src/isolate.h
File src/isolate.h (right):

https://chromiumcodereview.appspot.com/11970009/diff/1/src/isolate.h#newcode1074
src/isolate.h:1074: // to create a Locker for the first time (the lock itself is
in the isolate).
On 2013/01/17 10:53:18, Michael Starzinger wrote:
> I guess in the long run this method should disappear completely. Can we add a
> TODO about that?

Done.