On Tue, Nov 5, 2013 at 9:25 AM, jean bao <[email protected]> wrote: > I'm a beginner on V8, and I noticed this commit when I was reading about > V8's heap and heap object. > Could you please tell me the motivation of these changes? > Are these assertions just unnecessary? Or does V8 weaken the barrier > between Isolates by allowing access to another Isolate in current one? >
The whole notion of "current Isolate" will be removed, it was and endless source of bugs and pain. Whenever you need an Isolate, you should have it available as a parameter/member/etc., either directly or indirectly (e.g. via HeapObject::GetIsolate). Maintaining a barrier between Isolates will always be important because of correctness and security reasons. -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
